Don't try to delist a track-connection-by-tx connection that is already broken and has been closed. --------------------------------------------------------------------------------------------------- Key: JBAS-1636 URL: https://jira.jboss.org/browse/JBAS-1636 Project: JBoss Application Server Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: JBossAS-3.2.7 Final, JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1, JBossAS-4.0.2RC1 Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossAS-4.0.2 Final The transaction synchronization that returns track-connection-by-tx should not try to process connections that are broken and have already been closed. This leads to a spurious error message: org.jboss.resource.connectionmanager.TxConnectionManager - The re is something wrong with the pooling? java.lang.IllegalStateException: afterCompletion called with wrong tx! Expected: null, actual: TransactionImpl:XidImpl [...] at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventLi stener$TxRemover.afterCompletion(TxConnectio nManager.java:588) The error message does not cause problems but it can be noisy/disconcerting in the logs.