Chapter 12 Runtime Monitoring

Using the OTS Transaction Monitor

You can monitor and administer transactions on a single server from Jaguar Manager. You must be connected to the server before you can monitor or administer it.

Administering OTS/XA transactions

Select OTS Transaction Viewer for a server. The dialog displays the following information for all incomplete transactions. Because the OTS Transaction Viewer captures the information about incomplete transactions at a particular moment, you need to refresh the OTS Transaction Viewer to see any changes in the incomplete transaction status or any changes that you have made directly in the OTS Transaction Viewer.

Transaction ID The local identifier associated with the transaction on a specific server.
Family ID The identifier of the root transaction that this transaction belongs to.
Because EAServer does not support nested transactions, the Family ID is the same as the Transaction ID.

State Describes the status of the transaction and can be:

State	Description
`active`	The transaction is currently active in the server.
`inactive`	The transaction is not currently active in the server.
`preparing`	The transaction is in the process of being prepared.
`prepared`	The transaction has been prepared.
`committing`	The transaction is in the process of being committed.
`committed`	The transaction has been committed.
`commit_complete`	The transaction has committed and all participants have been informed, but the outcome may not have been reported to the transaction originator. For example, there may have been heuristic outcomes.
`before_abort`	The transaction has rolled back but has not yet started the rollback process.
`aborting`	The transaction is in the process of rolling back.
`aborted`	The transaction has been rolled back.
`abort_complete`	The transaction has rolled back and all participants have been informed, but the outcome may not have been reported to the transaction originator. For example, there may have been heuristic outcomes.
`finished`	The transaction has completed.
`none`	The server knows about the transaction, but the server is not a participant in the transaction.
`present`	The transaction is active in the server but is not yet a participant in the transaction.

You can roll back transactions only if they are not yet in the prepared state. You can execute all other operations only on transactions that have been prepared.

Lock Holder The transaction that holds the lock.
Lock Waiter The transaction that is waiting for a lock to be released.
Level An integer that represents the level of a nested transaction. Since EAServer does not support nested transactions, this field is always 1.

In the dialog that displays, select a transaction and click one of these buttons:
- Refresh List Refresh the list of all unfinished transactions.
- Rollback Roll back the entire transaction, including any sub-transactions.
  EAServer does not currently support nested OTS/XA transactions (also called subtransactions).
- Force Complete Force the transaction's rollback or commit processing (whichever outcome the transaction coordinator determined for the transaction) to be completed.
- Heuristic Commit Perform a heuristic commit.
- Heuristic Rollback Perform a heuristic rollback.
- Global Info Displays the global transaction identifier and the identifier of the application that started the transaction.