The Implementation of ActiveMQResourceAdapter.getXAResources() is broken.
Its internal call to makeConnection() creates a non-XA ActiveMQConnectionFactory which is then discarded as this ConnectionFactory is not XA-aware. As a result an empty XAResources array is returned.
This causes transaction recovery in the application server to fail.
Where the resource adapter can be manually configured (with beans for example) it is possible to work around by injecting the connection factory as an XA aware variant.