Transaction Details
Tasks Related Topics Attributes
Overview
The Transaction Details page shows details for the selected transaction. For transactions that may need to be manually resolved, you can click the Commit or Rollback options at teh bottom of the page. These options are restricted by the overall status of the transaction. See Table 53-1 for a list valid states and permitted transaction resolutions.
Tasks
To Manually Resolve a Transaction
Related Topics
Manually Resolving Current (Inflight) Transactions
Attributes
Transaction Id - The transaction identifier assigned by the Transaction Manager.
Coordinator - The name of the server that acts as the transaction coordinator for the transaction. The server name is qualified by the domain in which the server runs.
Name - The transaction name as specified in the application that created the transaction.
Status - The overall status of the transaction. This status determines the allowable transaction resolution options: commit or rollback. For valid states and related transaction resolution options, see Table 53-1.
Seconds Active - The number of seconds since the transaction was created.
Servers And Status - A list of all servers that participate in the transaction and the status for each server.
Resources - A list of resources that participate in the transaction and the status for each resource. A resource can be any XA-enabled resource registered with the Transaction Manager, such as a JDBC connection pool or a JMS store.
Properties - A list of transaction properties as defined by the application that created the transaction.
Force Local Rollback - Click this option to issue a rollback operation for the specified transaction on each participating resource that is registered on the current server. The transaction will then be removed from the local transaction manager's data structures.
Force Global Rollback - Click this option to issue a local rollback operation at each participating server for the specified transaction. If this option is invoked on a non-coordinating server, the coordinator will be contacted to process the operation. The coordinating server will issue asynchronous requests to each participant server.
Force Local Commit - Click this option to issue a commit operation for the specified transaction on each participating resource that is registered on the current server. The transaction will be removed from the local transaction manager's data structures. If the local server is the coordinator for the transaction, the commit record is released.
Force Global Commit - Click this option to issue a local commit operation at each participating server for the specified transaction. If this option is invoked on a non-coordinating server, the coordinator will be contacted to process the operation. The coordinating server will issue asynchronous requests to each participating server.
|
|
|