WAS v8.5 > Reference > SetsTransactions retrying resources
Use this page to review transactions with resources being retried.
If the transaction manager has prepared resources, but has lost contact with the resource managers before committing them or aborting them, then the transaction manager retries the commit or rollback requests to the affected resource managers. The number of times and frequency the transaction manager retries such commit or rollback requests is configured on the Heuristic retry limit and Heuristic retry wait properties of the transaction service settings.
An administrator can use this page to make the transaction service abandon the retries of one or more transactions. If a resource manager cannot be contacted, WebSphere Application Server relegates that resource manager to an in-doubt (prepared) state. The administrator then needs to use mechanisms specific to the resource manager to resolve the in-doubt status.
To view this dmgr console page, click Servers > Server Types > WebSphere application servers > [Content pane] server_name > [Container Settings] Container Services > Transaction Service > Runtime > Retry 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, select the check boxes next to the transactions to act on, then use the buttons provided.
- Local ID
- The local identifier of the transaction.
- Status
- The status of the transaction, 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- Global ID
- The global identifier of the transaction.
- Buttons
- Finish
- Stop retrying resources for the selected transactions.
Related
Manage active and prepared transactions
Related information:
Transaction resources