Chapter 7. JBoss Messaging XA Recovery Configuration

This section describes how to configure JBoss Transactions to handle XA recovery for JBoss Messaging resources in JBoss Enterprise Application Platform.
The JBoss Transactions Recovery Manager can be configured to continually poll for and recover JBoss Messaging XA resources. This provides a high level of transaction durability.
To enable JBoss Transactions Recovery Manager, add a line to $JBOSS_HOME/server/$PROFILE/conf/jbossts-properties.xml. The following code snippet includes the line required: 
<properties depends="arjuna" name="jta">
  <!--
  Support subtransactions in the JTA layer?
  Default is NO.
  -->
  <property name="com.arjuna.ats.jta.supportSubtransactions" value="NO"/>
  <property name="com.arjuna.ats.jta.jtaTMImplementation"
      value="com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple"/>
  <property name="com.arjuna.ats.jta.jtaUTImplementation"
      value="com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple"/>      
  <!--
      *** Add this line to enable recovery for JMS resources using DefaultJMSProvider ***
  -->
  <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1"
      value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery;java:/DefaultJMSProvider"/>

</properties>
Here, the Recovery Manager attempts to recover JMS resources via the JMS Provider Loader, DefaultJMSProvider.
DefaultJMSProvider ships with JBoss Enterprise Application Platform. It is defined in $JBOSS_HOME/server/$PROFILE/conf/jms-ds.xml (or, in a clustered environment, hajndi-jms-ds.xml). To perform recovery with a different JMS provider loader (for example, one that corresponds with a remote JMS Provider), add another line to the properties file and specify your remote provider instead of DefaultJMSProvider. Your provider's name should be listed in its managed bean configuration file.
Each provider requires a unique name, for example, com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1, com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING2, etc.
Recovery should work with any JMS provider that implements recoverable XAResources (that is, it properly implements XAResource.recover()).
For the Recovery Manager to recover from any node of the cluster, you must add a line in hajndi-jms-ds.xml for every node of the cluster.