Version 1

    There is a bug ( https://jira.jboss.org/jira/browse/JBAS-4675 ) that was fixed in 4.2.2, that coupled with the Cached Connection Manager can cause a connection leak.

     

    The bug https://jira.jboss.org/jira/browse/JBAS-4675 that was fixed in Jbosstm 4.2.3 sp7, https://jira.jboss.org/jira/browse/JBTM-289.

     

    The signature for this bug is...

     

    2007-09-05 17:50:44,899 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with transaction
    java.lang.IllegalStateException: Transaction not active
             at com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
             at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
             at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
             at org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
             at org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
             at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
             at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
             at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
             at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)

     

    This can cause a leak when using the debug feature in the CachedConnection manager.  When debug is turned off the leak goes away.