Mauro Molinari [http://community.jboss.org/people/mauromol] created the discussion "Bug JBTM-532 and JBoss Transactions 4.11" To view the discussion, visit: http://community.jboss.org/message/561793#561793 -------------------------------------------------------------- Hello, I recently upgraded JBossTS from 4.6.1 GA to 4.11 Final. I see that bug JBTM-532 that I opened against 4.5 and 4.6 should have been fixed in 4.8.0. However, I have a doubt on the current implementation of com.arjuna.ats.internal.jdbc.ConnectionImple.close(). I mean, if _theModifier is null, a comment says: "no indication about connections, so assume close immediately". However in this case only _theConnection is closed and set to null, while _recoveryConnection.closeCloseCurrentConnection() is not called. I think this may lead to connection leaks. What I would expect is that if _theModifier is null, a log entry were added but nothing else were done; in particular I would expect not to return and let the following "if (!delayClose)" (towards the end of the method) close the connections immediately (both _theConnection and _recoveryConnection). Before diving in debugging our application while monitoring the DBMS, I would like to know what JBossTS developers think about this and if I should open a JIRA. Thanks in advance, Mauro. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/561793#561793] Start a new discussion in JBoss Transactions Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]