The transaction service allows the client to freeze the transaction subsystem in order to roll back transactions and determine which transactions are in process at the time of the freeze. The transaction service fits into the tree of objects as shown in Transactions Service Tree Hierarchy.
Use the following dotted name pattern for transaction service statistics:
server.transaction-service.statistic
The statistics available for the transaction service are shown in the following table.
Table 8–35 Transaction Service Monitoring Statistics
Statistic |
Data Type |
Description |
---|---|---|
activecount |
CountStatistic |
Number of transactions currently active. |
activeids |
StringStatistic |
The ID’s of the transactions that are currently active. Every such transaction can be rolled back after freezing the transaction service. |
committedcount |
CountStatistic |
Number of transactions that have been committed. |
rolledbackcount |
CountStatistic |
Number of transactions that have been rolled back. |
state |
StringStatistic |
Indicates whether or not the transaction has been frozen. |