[ http://issues.apache.org/jira/browse/JCR-430?page=all ]
Dominique Pfister resolved JCR-430:
-----------------------------------
Fix Version: 1.0.1
Resolution: Duplicate
Sorry, I did not pay attention to the "Affect Versions" field. You're
absolutely right that this bug occurs in 1.0. Actually, it is a duplicate of
JCR-395. I suggest you either wait for the next, upcoming release of 1.0.1 or
work with the source of the main branch.
> 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
> Fix For: 1.0.1
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
