Transactions imported and prepared
To review transactions that have been imported and prepared but not yet committed.
Under normal circumstances no admin action is required for any of the transactions listed on this page. This page lists those transactions that are in a prepared state, but are being directed by an external transaction manager (for example, another WebSphere application server) from a transaction context that has been propagated.
Under aberrant circumstances, however, an administrator can configure WAS to resolve the transactions listed on this page independent of the external transaction manager. (This step might be necessary if, for example, the external transaction manager has become unavailable for an unacceptable period of time.)
If the completion direction (commit or rollback) chosen administratively differs from the eventual direction of the external transaction manager, then the overall outcome of the transaction is not atomic and data corruption can result.
To view this admin console page ...
Servers > Server Types > WebSphere application servers [Content pane] server_name > [Container Settings] Container Services > Transaction Service > Runtime > Imported prepared transactions - Review.
To list the resources used by a transaction, click the transaction local ID in the list displayed.
To act on one or more of the transactions listed, click the check boxes next to the transactions to act on, then use the buttons provided.
- Local ID
- The local identifier of the transaction.
- Global ID
- The global identifier of the transaction.
- Buttons
- Commit
- Heuristically commit the selected transactions.
- Rollback
- Heuristically roll back the selected transactions.
Related tasks
Manage active and prepared transactions
Related information
Transaction resources
Transaction service settings