Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <7134819.1180539555803.JavaMail.jira@brutus>
Date: Wed, 30 May 2007 08:39:15 -0700 (PDT)
From: "Xiaohua Lu (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Closed: (JCR-944) potential memory leak
In-Reply-To: <16058078.1180100296322.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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.