[EEPUBLISH-22] TransactionalJcrLockManager is not shared across publication operations Created: 24/Oct/19  Updated: 29/Mar/22  Resolved: 04/Nov/19

Status: Closed
Project: Publishing Transactional
Component/s: None
Affects Version/s: 1.0, 1.0.1, 1.0.2, 1.0.3
Fix Version/s: 1.0.4

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

Issue Links:
causality
is causing EEPUBLISH-25 Downgrade dependency on publishing mo... Closed
dependency
is depended upon by PUBLISHING-68 Synchronization issues Closed
is depended upon by PUBLISHING-73 Synchronization issues (backport to 1... 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
Sprint: SPA Editor 9, SPA Editor 10
Story Points: 0.5
Team: Nucleus

 Description   

Every publication request creates new instance of TransactionalJcrLockManager; such behavior is not necessary and adds undesired performance overhead. TransactionalJcrLockManager should be marked as Sinleton like it's parent class (JcrLockManager).


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