I would like ask for creating a section about limitation of XA transaction recovery for 3rd party messagings. This section was before part of XA datasource chapter (see doc 6.4 https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#sect-XA_Recovery - Vendor-specific issues and their consequences)

Section that I ask for being added to messaging guide should be about messaging and the text should contain:

This section describes the currently known messaging broker specific issues connected with handling XA transactions. These issues refers to jms broker and resource adapter versions which are currently supported by particular EAP version.

IBM Websphere

When JTS is used then second call of rollback against the same XID during the periodic recovery can cause an error to be logged in the log file. Second rollback against the same XID is JTS complaint and can be ignored.
When RAR does not know such XID, then XAER_NOTA return code is expected. But IBM Websphere may return an incorrect return code XAER_RMFAIL.

The method 'xa_rollback' has failed with errorCode '-7' due to the resource being closed.'

A-MQ

Resource adapter returns XAER_RMERR when an error occurs during the call of commit method protocol, for example network disconnection. Resource adapter returns this error code back to transaction manager and it causes the transaction being left in in-doubt state on message broker side. This behaviour is against XA specification and the correct return code should be XAER_RMFAIL or XAER_RETRY. The wrong error code can cause data inconsistency in some cases. For more information, refer to https://developer.jboss.org/thread/251537.

WARN [com.arjuna.ats.jtax] ...: XAResourceRecord.rollback caused an XA error: ARJUNA016099: Unknown error code:0 from resource ... in transaction ...: javax.transaction.xa.XAException: Transaction ... has not been started.