![]() |
|
|
|
|
Change By:
|
Jan Haderka
(14/Oct/13 3:48 PM)
|
|
Description:
|
When opening page w
In clustered environment or in environments with high load we have to expect concurrent attempts to create
/
autogenerated component for the first time, template renderer will trigger autogeneration
modify nodes
.
If there are multiple requests
Currently one such place (specially
for
display of the same
programatically created pages) is area auto-generation that is triggered on first
page
, one will fail with {{InvalidItemStateException}} or with {{ItemNotFoundException}} depending in which phase of autogeneration error occurs
rendering
.
Existing code
This issue
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
provide proof-
of
reaching race condition, it still exists and should
-concept for generic locking mechanism that could
be
avoided.
Solution
used
here should outline
throughout
the
way for general mechanism to handle concurrent editing once full author clustering is supported
application
.
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------
