Details
-
Bug
-
Resolution: Fixed
-
Neutral
-
4.5
-
None
-
-
Empty show more show less
-
Yes
-
5.1.1
Description
In clustered environment or in environments with high load we have to expect concurrent attempts to create/modify nodes. Currently one such place (specially for programatically created pages) is area auto-generation that is triggered on first page rendering. This issue attempts to provide proof-of-concept for generic locking mechanism that could be used throughout the application.
Checklists
Attachments
Issue Links
- is depended upon by
-
MAGNOLIA-5351 Moved or deleted items (pages, components) do NOT update activation status
-
- Closed
-
-
MAGNOLIA-5385 Make Autogeneration thread/clustering safe
-
- Closed
-
- is related to
-
MAGNOLIA-5191 Occasional ItemNotFoundException when trying to autogenerate area
-
- Closed
-
-
MAGNOLIA-5432 Do not remove mix:lockable while versioning nodes
-
- Closed
-
- mentioned in
-
Wiki Page Loading...