In previous versions of EAP 6, if an XA transaction involving HornetQ timed out, it was possible that HornetQ might throw a `non-XAException` to the Transaction Manager.
The issue was identified in the implementation of
`javax.transaction.xa.XAResource`, and has been resolved in this release.
+++ This bug was initially created as a clone of Bug #1088606 +++
Should be fixed by upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1064596 for DR2
Verified in EAP 6.3.0.ER7 / HornetQ 2.3.19.Final