There exists a race condition in the transaction manager such that we may call start on an XAResource but never call end (or anything else) on it. In other words, we may leave the resource manager (jms, db, jca) in a bad state.

Per support case i-t #171373 this is known to affect JCA connectors but almost certainly also affects any other usage of XA transactions.

The fix will at minimum require changes to the transaction manager, per JBTM-354

More generally however, the AS was written with the assumption of synchronous rollback of timed out transactions. The asynchronous approach used by JBossTS is known to cause issues in the AS codebase, e.g. JBAS-5095 and it may be advisable to audit the app server JCA and other transaction using AS code for similar issues.