Use this task to manage active and prepared transactions that might
need administrator action.
About this task
Under normal circumstances, transactions
should run and complete (commit or roll back) automatically, without the need
for intervention. However, in some circumstances, you might have to resolve
a transaction manually. For example, you might want to roll back a transaction
that has become stuck polling a resource manager that you know will not become
available again within the required timeframe.
Under normal
circumstances, every effort is made to finish a transaction. However, due
to RRS and native contexts finishing, finishing the transaction might not
be possible. In this case, the transaction is marked rollback_only so that
it rolls back at the next available window. In other situations, you might
have to finish a transaction manually. For example, you might want to finish
a transaction that has become stuck polling a resource manager that you know
will not become available again within the required timeframe.
Note: If
you choose to complete a transaction on an application server, it is recorded
as having completed in the transaction service logs for that server, so will
not be eligible for recovery during server start up. If you complete a transaction,
you are responsible for cleaning up any in-doubt transactions on the resource
managers affected.
You can use the administrative console to display
a snapshot of all the transactions in an application server that are in the
following states:
- Manual transactions
- Transactions awaiting administrative completion. For each transaction,
the local id or global id is displayed. You can choose to display information
on each resource (specifically, which resource manager it is associated with)
associated with the transaction. You can also choose to commit or roll back
transactions in this state.
- Retry transactions
- Transactions with some resources being retried. For each transaction,
the local id or global id is displayed, and whether the transaction is committing
or rolling back. You can choose to display information on each resource (specifically,
which resource manager it is associated with) associated with the transaction.
You can also choose to finish (stop retrying) transactions in this state.
- Heuristic transactions
- Transactions that have completed heuristically. For each transaction,
the local id or global id and the heuristic outcome is displayed. You can
choose to display information on each resource (specifically, which resource
manager it is associated with) associated with the transaction. You can also
choose to clear the transaction from the list.
- Imported prepared transactions
- Transactions that have been imported and prepared but not yet committed.
For each transaction, the local id or global id is displayed. You can choose
to display information on each resource (specifically, which resource manager
it is associated with) associated with the transaction. You can also choose
to commit or roll back transactions in this state.
To manage the active and prepared transactions for an
application server, use the administrative console to complete the following
steps: