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 that 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.
WebSphere Application Server for z/OS can relegate the resource
manager to an in-doubt (prepared) state only if the RRS transaction
context is available.
To view this administrative console page, click
> [Content pane] server_name > .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 that you want to act on, then use the buttons provided.
0 - active
1 - marked for rollback
2 - prepared
3 - committed
4 - rolled back
5 - unknown
6 - none
7 - preparing
8 - committing
9 - rolling back