12.5. Overview of JTA Transactions
12.5.1. About Java Transactions API (JTA)
12.5.2. Lifecycle of a JTA Transaction
Your application starts a new transactionTo begin a transaction, your application obtains an instance of class
UserTransactionfrom JNDI or, if it is an EJB, from an annotation. The
UserTransactioninterface includes methods for beginning, committing, and rolling back top-level transactions. Newly-created transactions are automatically associated with their invoking thread. Nested transactions are not supported in JTA, so all transactions are top-level transactions.Calling
begin()using annotations starts a transaction when an EJB method is called (driven by TransactionAttribute rules). Any resource that is used after that point is associated with the transaction. If more than one resource is enlisted, your transaction becomes an XA transaction, and participates in the two-phase commit protocol at commit time.
UserTransactionobject is used only for BMT transactions. In CMT, the UserTransaction object is not permitted.
Your application modifies its state.In the next step, your application performs its work and makes changes to its state.
Your application decides to commit or roll backWhen your application has finished changing its state, it decides whether to commit or roll back. It calls the appropriate method, either
The transaction manager removes the transaction from its records.After the commit or rollback completes, the transaction manager cleans up its records and removes information about your transaction from the transaction log.
Failure recovery happens automatically. If a resource, transaction participant, or the application server become unavailable, the Transaction Manager handles recovery when the underlying failure is resolved and the resource is available again.