jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Pfister (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-430) Memory leak when using transactions
Date Wed, 10 May 2006 10:38:05 GMT
    [ http://issues.apache.org/jira/browse/JCR-430?page=comments#action_12378880 ] 

Dominique Pfister commented on JCR-430:

Thank you for reporting this issue. 

I looked at the source code of your test class and found that the actual cause for the OutOfMemoryError
is the TransientRepository being used in your sample. Every time your session logs in, the
repository is started and shut down again when your session logs out. Every iteration uses
up around 6MB, so this is definitely a memory leak. But this happens regardless whether you
use transactions or not, so apparently this is the wrong component to blame.

> Memory leak when using transactions
> -----------------------------------
>          Key: JCR-430
>          URL: http://issues.apache.org/jira/browse/JCR-430
>      Project: Jackrabbit
>         Type: Bug

>     Versions: 1.0
>     Reporter: Nicolas Belisle
>     Assignee: Tobias Bocanegra
>     Priority: Critical
>  Attachments: TransactionTest.java
> Using a sequence of transactions resolve in a java.lang.OutOfMemoryError. 
> I'm using UserTransactionImpl found in /src/test. Could be the cause of the problem...
> An example will follow shortly. Note that in the example, if you remove the transaction
context, no leak arises.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message