[PUBLISHING-109] Concurrent modification of same nodes in #onSendDone leads to InvalidItemStateException Created: 23/Mar/21  Updated: 20/Jul/22  Resolved: 29/Apr/21

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1.9, 1.2.6

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 0.25d
Original Estimate: Not Specified

Issue Links:
Relates
relates to PUBLISHING-99 Move away from JCR node locking Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: Nucleus Quality Maintenance
Sprint: HL & LD 25, HL & LD 26, HL & LD 27, HL & LD 28
Story Points: 5
Team: Nucleus

 Description   

This use case may lead to the InvalidItemStateException:

 node1 is published by thread T1
 node1 is retrieved from session and is being prepared for publication by thread T2
 node1 metadata updated and session saved by T1
 node1 export fails on T2 because of changes in metadata by T1 -> InvalidItemStateException
 T2 fails to publish the node  

Issue became more visible after implementing PUBLISHING-99.


Generated at Mon Feb 12 10:35:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.