7.3. Cluster Notes

Each application server instance is responsible for recovering transactions it was coordinating. Commonly, a single database serves multiple application servers, and thus participates in transactions from multiple coordinators. During recovery, JBoss Transaction Service requests a list of in-doubt transactions which it can potentially recover, from each application server. The database returns all in-doubt transactions, including ones that may not have been coordinated by a given instance. To effectively separate each node's transactions, you must configure a unique node id for each application server instance that shares a common database, by setting a unique value for the following property:

<property name="com.arjuna.ats.arjuna.xa.nodeIdentifier" value="1"/>

<property name="com.arjuna.ats.arjuna.xa.nodeIdentifier" value="1"/>

You also need an element that indicates what node needs the recovery. This needs to match the nodeIdentifier configured above.

<property name="com.arjuna.ats.jta.xaRecoveryNode" value="1"/>

<property name="com.arjuna.ats.jta.xaRecoveryNode" value="1"/>