[PUBLISHING-68] Synchronization issues Created: 17/Oct/19  Updated: 29/Mar/22  Resolved: 12/Nov/19

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: 1.1.1
Fix Version/s: 1.1.3

Type: Bug Priority: Blocker
Reporter: Mercedes Iruela Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by PUBLISHING-73 Synchronization issues (backport to 1... Closed
causality
dependency
depends upon EEPUBLISH-22 TransactionalJcrLockManager is not sh... 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:
Epic Link: Support
Sprint: SPA Editor 9, SPA Editor 10
Story Points: 8
Team: Nucleus

 Description   

Execution of publication / unpublication / commit / rollback needs to be synchronized (info.magnolia.publishing.dispatcher.AbstractDispatcher).

In consequence, due to the locks, nodes are cleaned by the publication module and only part of the content / or no content is imported.



 Comments   
Comment by Jarkko Mantysaari [ 21/Oct/19 ]

Any estimate that when this Jira ticket will be resolved. ? It will be good know the estimated timeline for bug fix as it still seems to be unassigned. 

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