Manage active transactions

In the administrative console, you can display a list of all transactions that are currently running on an application server. For each transaction, the local ID, global ID, and current status are displayed. 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

See Transaction states for more information about transaction states.

You can also finish transactions manually. Under normal circumstances, transactions run and complete (commit or rollback) automatically. However, in some circumstances, you might need to finish a transaction manually. For example, you might want to finish a transaction if it is polling a resource manager that is currently unavailable and is likely to remain unavailable for an extended period of time.

Note: If you choose to finish a transaction on an application server, it is recorded as a completed transaction in the transaction service logs. As a result, the transaction is not available for recovery during server start up. If you finish a transaction, manually clean up any questionable transactions on the resource managers affected.

To manage the active transactions for an application server, perform these steps:

1. Start the administrative console.
2. In the topology tree, expand Servers, and click Application Servers.
3. On the Application Servers page, click the name of the application server that you want to modify.
4. Click the Runtime tab.
5. Click Transaction Service.
6. Click Manage Transactions. For each transaction, the local ID, current status, and global ID are displayed.
7. If you want to finish one or more transactions, select the checkbox provided on the entry for the transaction, and click Finish. To finish all transactions, select the checkbox in the header of the transactions table, and click Finish.