[
https://issues.apache.org/jira/browse/JCR-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682266#action_12682266
]
Przemo Pakulski commented on JCR-2023:
--------------------------------------
During initialization of workspace SharedItemStateManager is registeres as
listener fro virtual item state providers, by the following code :
// create item state manager
try {
itemStateMgr = createItemStateManager(persistMgr, rootNodeId,
ntReg, true, cacheFactory, ismLocking);
try {
itemStateMgr.addVirtualItemStateProvider(
vMgr.getVirtualItemStateProvider());
itemStateMgr.addVirtualItemStateProvider(
virtNTMgr.getVirtualItemStateProvider());
} catch (Exception e) {
log.error("Unable to add vmgr: " + e.toString(), e);
}
When workspace is disposed SharedItemStateManager should be deregistered from
virtual item state providers to aloow JVM to free memory.
> WorkspaceInfo.dispose() does not deregister SharedItemStateManager from
> virtual item state providers
> ----------------------------------------------------------------------------------------------------
>
> Key: JCR-2023
> URL: https://issues.apache.org/jira/browse/JCR-2023
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.5.4, 1.6.0
> Reporter: Przemo Pakulski
> Assignee: Przemo Pakulski
>
> Automatic disposal of idle workspaces frees unused workspaces but
> corresponding SharedItemStateManager (and releated PersistenceManager) is
> still kept in memory referenced by virtual item state providers, this can
> lead to memory leaks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
