Can document this issue to release notes. More info in: https://issues.jboss.org/browse/JBPAPP-11092

"There is warning during start and stop of EAP 5.3.0.ER1 server:

13:46:24,655 WARN  [loggerI18N] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery  got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/DefaultJMSProvider, XAException.XAER_RMERR
13:46:32,652 INFO  [ServerPeer] JBoss Messaging 1.4.8.SP10 server [0] started
13:46:33,977 INFO  [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
13:46:33,977 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@6bd79538 started

Problem seems to be that transaction manager is trying periodic recovery and JBoss Messaging was not yet started.

In trace log for com.arjuna there is:

2014-04-08 13:46:24,464 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (main) TransactionReaper::remove ( BasicAction: 7f000001:8fd0:5343e186:26 status: ActionStatus.ABORTED )
2014-04-08 13:46:24,464 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (main) TransactionReaper::insert ( BasicAction: 7f000001:8fd0:5343e186:29 status: ActionStatus.RUNNING, 300 )
2014-04-08 13:46:24,650 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (Thread-19) Periodic recovery - second pass <Tue, 8 Apr 2014 13:46:24>
2014-04-08 13:46:24,650 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (Thread-19) AtomicActionRecoveryModule: Second pass 
2014-04-08 13:46:24,650 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] (Thread-19) [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_6] - TORecoveryModule - second pass
2014-04-08 13:46:24,650 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] (Thread-19) [com.arjuna.ats.internal.jta.recovery.info.secondpass] Local XARecoveryModule - second pass
2014-04-08 13:46:24,655 WARN  [com.arjuna.ats.jta.logging.loggerI18N] (Thread-19) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery  got XA exception javax.transaction.xa.XAEx
ception: Error trying to connect to provider java:/DefaultJMSProvider, XAException.XAER_RMERR
2014-04-08 13:46:24,868 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (main) TransactionReaper::remove ( BasicAction: 7f000001:8fd0:5343e186:29 status: ActionStatus.ABORTED )
2014-04-08 13:46:24,869 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (main) TransactionReaper::insert ( BasicAction: 7f000001:8fd0:5343e186:2d status: ActionStatus.RUNNING, 300 )
2014-04-08 13:46:25,272 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (main) TransactionReaper::remove ( BasicAction: 7f000001:8fd0:5343e186:2d status: ActionStatus.ABORTED )
2014-04-08 13:46:25,273 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (main) TransactionReaper::insert ( BasicAction: 7f000001:8fd0:5343e186:30 status: ActionStatus.RUNNING, 300 )

I could simulate this problem easily when mysql databse was configured as DefaultDS for JBM."