The error message says it can't enlist the connection in the transaction because
something has set the transaction to rollback only.
10:07:42,812 ERROR [HornetQRASessionFactoryImpl] Could not create session
javax.resource.ResourceException: Transaction is not active: tx=TransactionImple < ac, BasicAction: -53edf53a:5e0:4ba99350:a3 status: ActionStatus.ABORT_ONLY
>
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:370)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
at org.hornetq.ra.HornetQRASessionFactoryImpl.allocateConnection(HornetQRASessionFactoryImpl.java:837)
at org.hornetq.ra.HornetQRASessionFactoryImpl.createSession(HornetQRASessionFactoryImpl.java:470)
at wipo.csc.jms.cluster.ejb.ClusteredQueueEJBListener.sendMessage(ClusteredQueueEJBListener.java:135)
So you need to find out what is doing setRollbackOnly() on the transaction.
e.g. invoking a CMT EJB in the same transaction that throws a RuntimeException would do that.
Nothing in JCA ever sets the status of the transaction to rollback only.