[PUBLISHING-25] Synchronisation in JcrLockManager leads to long waiting time when publishing a lot of nodes under same root Created: 01/Nov/17  Updated: 29/Mar/22  Resolved: 02/Nov/17

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

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

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
Sprint: Kromeriz 120
Team: Nucleus

 Description   

The synchronisation block present in the JcrLockManager is not necessary, it only leads to long waiting times when publishing multiple nodes under same parent.


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