[
http://jira.magnolia.info/browse/MAGNOLIA-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory Joseph updated MAGNOLIA-2159:
-------------------------------------
Summary: session can be closed if LazyContentWrapper is used (was: session
can be closed if LazyConentWrapper is used)
> session can be closed if LazyContentWrapper is used
> ---------------------------------------------------
>
> Key: MAGNOLIA-2159
> URL: http://jira.magnolia.info/browse/MAGNOLIA-2159
> Project: Magnolia
> Issue Type: Bug
> Affects Versions: 3.5.7, 3.6
> Reporter: Philipp Bracher
> Assignee: Philipp Bracher
> Priority: Critical
> Fix For: 3.5.8, 3.6
>
>
> It is the nature of the LazyContentWrapper to refetch the wrapped node again
> if the session has been closed. That is fine. If you then access children
> later it might be that the former session has been closed because it has been
> handled by another thread:
> - thread1 creates session1
> - thread1 uses LazyContentWrapper so the node is bound to session1
> - thread2 creates session 2
> - thread2 uses LazyContentWrapper but session1 is still open and so used
> - thread2 gets a child of the node (this child node is of type DefaultContent)
> - thread1 closes session1
> - thread2 tries to use the child node and it fails with a session closed
> exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
