You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Xiaohua Lu (JIRA)" <ji...@apache.org> on 2007/05/30 17:39:15 UTC
[jira] Closed: (JCR-944) potential memory leak
[ https://issues.apache.org/jira/browse/JCR-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaohua Lu closed JCR-944.
--------------------------
Resolution: Invalid
> potential memory leak
> ---------------------
>
> Key: JCR-944
> URL: https://issues.apache.org/jira/browse/JCR-944
> Project: Jackrabbit
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Xiaohua Lu
>
> we are doing some stress test and noticed instances of access manager and login manager we provided for Jackrabbit are not GCed.
> According to heap snapshot (from JProfiler), they are traced back to RepositoryImpl
> RepositoryImp -> HashMap -> RepositoryImpl$WorkspaceInfo -> SharedItemStateManager -> StateChangeDispatcher -> CopyOnWriteArrayList -> XAItemStateManager -> StateChangeDispatcher -> CopyOnWriteDispatcher -> SessionItemStateManager -> StateChangeDispatcher -> CopyOnWriteArrayList -> ItemManager -> XASessionImpl -> AuthContext -> our LoginModule Impl
> Since RepositoryImpl is always kept in memory, so all instances of our login module are not GCed even after requests have been served.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.