+

Search Tips   |   Advanced Search

 

Manage active and prepared transactions

 

Use this task to manage active and prepared transactions that might need administrator action.

 

Overview

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.

If you choose to complete a transaction on an appserver, 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 console to display a snapshot of all the transactions in an appserver 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 rollback 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 (abandon 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 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 rollback transactions in this state.

To manage the active and prepared transactions for an appserver, use the console to complete the following steps:

 

Procedure

  1. Display the Transaction Service runtime page for appserver:

    1. In the navigation pane, click Servers-> Application Servers

    2. In the content pane, click the name of the appserver

    3. In the content pane, click the Runtime tab.

    4. Under Additional Properties, click Transaction Service

    This displays values for the runtime properties of the transaction service, including the number of transactions in the active and prepared states.

  2. To display a snapshot of the transactions in a specific state, click Review in the field label.

     

  3. Optional: To display information about the resources associated with a transaction, click the name of the transaction.

     

  4. Optional: To act on a transaction, select the check box provided on the entry for the transaction, then click one of the buttons provided. Alternatively, to act on all transactions, select the check box in the header of the transactions table, then click a button.


 

Related tasks


Configure transaction properties for an appserver
Use the transaction service

 

Related information

Transactions needing manual completion
Transactions retrying resources
Transactions with heuristic outcome
Transactions imported and prepared