[jira] Commented: (JCR-1037) Memory leak causing performance problems

[Thomas Mueller (JIRA)]

    [ 
https://issues.apache.org/jira/browse/JCR-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518678
 ] 

Thomas Mueller commented on JCR-1037:
-------------------------------------

Hi,

So far I can't reproduce this problem. With my test case, I only got 6 caches:
09.08.2007 11:52:30 *INFO * [main] CacheManager: resizeAll size=6 
(CacheManager.java, line 125)
(size=6 means 6 caches)

import org.apache.jackrabbit.core.TransientRepository;
import javax.jcr.*;
public class TestVersioning {
    public static void main(String[] args) throws Exception {
        Session session = new TransientRepository()
                .login(new SimpleCredentials("", new char[0]));
        Node node = session.getRootNode().addNode("test");
        node.addMixin("mix:versionable");
        session.save();
        for (int i = 0; i < 10000; i++) {
            node.checkout();
            node.setProperty("x", i);
            session.save();
            node.checkin();
            if(i % 10 == 0) {
                System.out.println(i);
            }
        }
        session.logout();
    }
}

Do you use multiple sessions, workspaces, clustering, or any other special 
configuration?

Thanks,
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
>         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.