Chapter 4. Transaction Recovery
4.1. Failure recovery
XAResource.recovermethod to retrieve the list of transactions currently in a
heuristically completedstate. Typically, the system administrator configures all transactional resource factories that are used by the applications deployed on the system. The JDBC
XADataSourceobject, for example, is a factory for the JDBC
XAResourceobjects are not persistent across system failures, the Transaction Manager needs the ability to acquire the
XAResourceobjects that represent the resource managers which might have participated in the transactions prior to a system failure. For example, a Transaction Manager might use the JNDI look-up mechanism to acquire a connection from each of the transactional resource factories, and then obtain the corresponding
XAResourceobject for each connection. The Transaction Manager then invokes the
XAResource.recovermethod to ask each resource manager to return the transactions that are currently in a
*forces recovery, and possibly rollback, of all transactions, regardless of their node identifier. Use it with caution.
XAResourcecrash recovery automatically. Otherwise one, of the following recovery mechanisms is used:
- If the
XAResourceis able to be serialized, then the serialized form will be saved during transaction commitment, and used during recovery. The recreated
XAResourceis assumed to be valid and able to drive recovery on the associated database.
com.arjuna.ats.jta.recovery.XARecoveryResourceinterfaces are used. Refer to the JDBC chapters on failure recovery for more information.