[MGNLXAA-50] simultaneous activation of 1st and 2nd level page might cause failure to activate due incorrect locking Created: 24/Oct/12  Updated: 28/Nov/12  Resolved: 26/Nov/12

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: 1.2.4, 1.3.4
Fix Version/s: 1.2.5, 1.3.5

Type: Bug Priority: Blocker
Reporter: Jan Haderka Assignee: Ondrej Chytil
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-4593 simultaneous activation of 1st and 2n... 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

 Description   

When activating 1st level pages (home page) the root of the repo can't be locked and no JCR lock is issued for activation. If 2nd level page that exists under same path is activated at the same time, it would issue lock on the parent (1st level page) and thus lock it during the activation causing first activation to fail.



 Comments   
Comment by Jan Haderka [ 27/Oct/12 ]

Fixed on 1.2 branch, needs to be ported to master.

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