DB Connections leaked if TX is not active after retrieving a connection ----------------------------------------------------------------------- Key: JBJCA-1159 URL: https://issues.jboss.org/browse/JBJCA-1159 Project: IronJacamar Issue Type: Bug Components: Core Affects Versions: 1.0.19.Final Environment: AS7 EAP6.1 Reporter: gui borland Assignee: Jesper Pedersen Priority: Critical When a connection is retrieved from the MCP, ironjacamar will register it to ongoing JTA transaction. However, if the ongoing TX is not 'active' anymore the connection is lost. The code of AbstractPool demonstrates the problem. The call to getLock will throw an exception if the current TX is not active anymore and the cl is not returned to the pool. This issue can be reproduced on AS7 by using any EJB that requires a tx and does something with a DB connection. Put a breakpoint in the code below after retrieving the connectionlistener, and then wait for the transaction to timeout. Once that's done, continue the thread. The connection is not release (can be seen in JMX) We have noticed this problem regularly during our performance tests. {code} ConnectionListener cl = mcp.getConnection(subject, cri); if (trace) log.tracef("Got connection from pool tracked by transaction=%s tx=%s", cl, trackByTransaction); TransactionSynchronizationRegistry tsr = getTransactionSynchronizationRegistry(); Lock lock = getLock(); try { lock.lockInterruptibly(); } catch (InterruptedException ie) { Thread.interrupted(); throw new ResourceException(bundle.unableObtainLock(), ie); } {code} It seems this issue was introduced by changes done for https://issues.jboss.org/browse/JBJCA-572