-
Bug
-
Resolution: Fixed
-
Blocker
-
1.2.2
-
None
When two or more activation requests for same content are delivered to public instance in very short time window, and one of the requests fails due to collision (attempt to modify same content), Magnolia might treat such request as deactivation and remove content from public instance.
Acceptance criteria
- clones
-
MAGNOLIA-4408 Inadvert deactivation of the content during multiple concurrent activations
- Closed
- is causing
-
MGNLXAA-45 Activation of node marked for deletion fails on NPE
- Closed
- is related to
-
MGNLXAA-41 Add missing tests
- Closed