Use this task to manage transactions that are active on an application server.
Why and when to perform this task
You can use this task to display a snapshot of all the transactions currently running on an application server. For each transaction, the following properties are shown: its local ID, global ID, and current status. The transaction status is shown as an integer value. The values correspond to the following status:
0 - active 1 - marked for rollback 2 - prepared 3 - committed 4 - rolled back 5 - unknown 6 - none 7 - preparing 8 - committing 9 - rolling back
You can also choose to finish transactions manually.
Under normal circumstances, transactions should run and complete (commit or rollback) automatically, without the need for intervention. However, in some circumstances, you may need to resolve a transaction manually. For example, you may want to rollback a transaction that has become stuck polling a resource manager that you know will not become available again within the desired timeframe.
Note: If you choose to finish 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 finish a transaction, you are responsible for cleaning up any in-doubt transactions on the resource managers affected.
To manage the active transactions for an application server, use the administrative console to complete the following steps:
Steps for this task