[ http://jira.magnolia.info/browse/MAGNOLIA-1800?page=all ]
Andriy Shapochka resolved MAGNOLIA-1800.
----------------------------------------
Resolution: Fixed
Now HierarchyManagers are held threadlocally in HierarchyManagerLoaders in
ContentRepository. To factor out them from ContentRepository altogether would
have lead to too many changes in the code. So instead of storing
HierarchyManager instances in ContentRepository.hierarchyManagers we store the
loaders with the same keys
> SystemContext should not share the jcr session for all threads
> --------------------------------------------------------------
>
> Key: MAGNOLIA-1800
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1800
> Project: Magnolia
> Issue Type: Sub-task
> Affects Versions: 3.1 M3
> Reporter: Philipp Bracher
> Assigned To: Andriy Shapochka
> Fix For: 3.1
>
>
> The jcr session is not thread safe so it is wrong that all calls to
> MgnlContext.getSystemContext().getHierarchyManager() get the same object.
> This can be solved by implementing getSystemContext() very similar to
> MgnlContext.getInstance() by using a thread local. All this object have
> shared attributes, AccessManager, but acquire the jcr session
> (HierarchyManager) the same way as the other contexts do
--
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/docs/en/editor/stayupdated.html
----------------------------------------------------------------
