[MGNLXAA-88] Unpublishing right after publication can result in exception Created: 04/Dec/14  Updated: 28/Jan/15  Resolved: 28/Jan/15

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: 2.0
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Evzen Fochr Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLACTIVATION-99 Unpublishing right after publication ... 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   

Publishing a page tree might take some time. If this is the case and you're quick enough to trigger an unpublication of the same page tree, you might get an exception because Magnolia tries to deactivate something that wasn't properly activated yet (tested with ee 5.2.7 and 5.3.2). We should check how to prevent running into this situation. e.g. introduce a kind of dependencies between asynchronously executed action (only start second when the first is indeed finished).
Approach to solve this will be quietly ignore Exception for this case, and continue activation.

Solution approach depends on MGNLACTIVATION-99.



 Comments   
Comment by Evzen Fochr [ 28/Jan/15 ]

No changes needed, repair done in MGNLACTIVATION-99.

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