[LIVECOPY-218] ItemNotFound bei Push in LiveCopy Created: 30/Jul/20  Updated: 20/Aug/20  Resolved: 05/Aug/20

Status: Closed
Project: Live Copy
Component/s: None
Affects Version/s: 3.1.1
Fix Version/s: 3.1.2

Type: Bug Priority: Critical
Reporter: Arne Gerstaedt Assignee: Jesus Alonso
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by LIVECOPY-220 ItemNotFound in Push Master Changes Closed
dependency
is depended upon by LIVECOPY-224 Integrate LC 173,178 and 218 to master Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

PROJEKT RITTAL / HENKELHIEDL

When we push changes via Live-Copy from the source site to the specific copies we get an excpetional failure. This applies to sites with and without subnodes. 

FAILURE DESCRIPTION

RpcInvocationException: Unable to invoke method click in com.vaadin.shared.ui.button.ButtonServerRpc
caused by InvocationTargetException
caused by MethodException: Invocation of method buttonClick in info.magnolia.ui.AlertBuilder$$Lambda$1093/0x00000008413de440 failed.
caused by RuntimeException: info.magnolia.ui.api.action.ActionExecutionException: javax.jcr.ItemNotFoundException: b2d0babb-ab9f-428e-b5e5-0889271c379e
caused by ActionExecutionException: javax.jcr.ItemNotFoundException: b2d0babb-ab9f-428e-b5e5-0889271c379e
caused by ItemNotFoundException: b2d0babb-ab9f-428e-b5e5-0889271c379e
caused by NoSuchItemStateException: b2d0babb-ab9f-428e-b5e5-0889271c379e
caused by NoSuchItemStateException: b2d0babb-ab9f-428e-b5e5-0889271c379e

Further Explanations have been given on 29.th July to Jan Schulte and Jesus Alonso.



 Comments   
Comment by Jesus Alonso [ 05/Aug/20 ]

Customer has confirmed that the provided patch solves the issue

Generated at Mon Feb 12 02:26:36 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.