Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <7750391.1188202770524.JavaMail.jira@brutus>
Date: Mon, 27 Aug 2007 01:19:30 -0700 (PDT)
From: "Thomas Mueller (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-1037) Memory leak causing performance
 problems
In-Reply-To: <26822905.1185482823894.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-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Mueller resolved JCR-1037.
---------------------------------

    Resolution: Cannot Reproduce
      Assignee: Thomas Mueller

Hi,

I like to solve this problem, but can not reproduce it. In my view, we need a reproducible test case. We also need to know if the problem occurs with one session, or if many sessions are opened. 

Thomas

> Memory leak causing performance problems
> ----------------------------------------
>
>                 Key: JCR-1037
>                 URL: https://issues.apache.org/jira/browse/JCR-1037
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: Jackrabbit API
>    Affects Versions: 1.2.1, 1.2.2, 1.2.3, 1.3
>         Environment: Tomcat 6.0, XP Pro w/1Gb
>            Reporter: Antonio Carballo
>            Assignee: Thomas Mueller
>         Attachments: JCR-Trace.txt
>
>
> Folks,
> We have been running tests on JCR v1.3 and v1.2.1 for the past two weeks. The system keeps running out of memory after X number of documents are added. Our initial test consisted of about 50 documents and gradually increased to about 150 documents. The size of the documents ranged from 1K to 9MB. We later changed the test to consist of files with less than 1K in length with the same result. Increasing the heap size delays the error but the outcome is always the same (Servlet runs out of heap memory.)
> Using JProbe we found a high number of references created by the caching sub-system (SessionItemStateManager.java, SharedItemStateManager.java, LocalItemStateManager.java).  We changed the caching parameters using CacheManager (min 64K - max 16MB). This change only delayed the error. Servlet eventually runs out of heap memory.
> We are more than happy to share our findings (even source code and test data) with the Jackrabbit team. Please let us know how you wish to proceed.
> Sincerely,
> Antonio Carballo

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.