-
Bug
-
Resolution: Fixed
-
Neutral
-
4.5
-
None
When opening page w/ autogenerated component for the first time, template renderer will trigger autogeneration. If there are multiple requests for display of the same page, one will fail with InvalidItemStateException or with ItemNotFoundException depending in which phase of autogeneration error occurs.
Existing code attempts to work around the issue by hiding the exception and waiting for up to half second for autogenerated node to become visible. While this diminishes possibility of reaching race condition, it still exists and should be avoided.
Solution used here should outline the way for general mechanism to handle concurrent editing once full author clustering is supported.
- depends upon
-
MAGNOLIA-5362 Introduce mechanism for performing write operations safely in environment with high concurrency
- Closed
- is depended upon by
-
MAGNOLIA-5351 Moved or deleted items (pages, components) do NOT update activation status
- Closed
- is related to
-
MAGNOLIA-5191 Occasional ItemNotFoundException when trying to autogenerate area
- Closed
-
MAGNOLIA-5387 Updating last access date is not cluster/thread safe
- Closed
- mentioned in
-
Page Loading...