jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Przemo Pakulski (JIRA)" <j...@apache.org>
Subject [jira] Created: (JCR-395) Using transactions leads to memory leak
Date Wed, 12 Apr 2006 12:05:28 GMT
Using transactions leads to memory leak

         Key: JCR-395
         URL: http://issues.apache.org/jira/browse/JCR-395
     Project: Jackrabbit
        Type: Bug

  Components: transactions  
    Reporter: Przemo Pakulski

There is global static map in XASessionImpl class which stores all Xids and TransactionContexts

     * Global transactions
    private static final Map txGlobal = new HashMap();

It looks like this map is never cleared, even after end of transaction. It leads to memory
leak because TransactionContexts and all nested objects (including XASessionImpl) are still
referenced and couldn't be freed.

Proposed solution : Is it posssible to add just single line which will remove TransactionContext
from static map at the end of transaction ?

      if (flags == TMSUCCESS || flags == TMFAIL) {
-->       txGlobal.remove(xid);
        } else  if (flags == TMSUSPEND) {
        } else {
            throw new XAException(XAException.XAER_INVAL);

If this is not acceptable, then we have to unreference TransactionContext in another way.

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