Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Transactions by Resource

The Transactions by Resource table shows transaction statistics about for each transactional resource accessed on this server. You can click column headings in the table to sort the information in the table. You can also click Customize this view to select the columns to display in the table.

- For information about heuristic completions, see Handling Heuristic Completions.
- For information about configuring WebLogic JTA in the Administration Console, see Configuring JTA.
- To learn more about WebLogic JTA, see JTA and Programming WebLogic JTA.

## Attributes

The Transactions by Resource table includes the following columns:

Name—The resource name on the server. A resource is any XA-compliant resource that can participate in a distributed transaction, such as a connection pool or a JMS store.

Transactions—The number of transactions in which the resource participated.

Commits—The number of transactions in which the resource committed the transaction.

Rollbacks—The number of transactions in which the resource rolled back the transaction.

Heuristics—The number of transactions for which the resource reported a heuristic decision, either a heuristic commit, a heuristic rollback, a mixed heuristic decision, or a heuristic hazard decision. See Handling Heuristic Completions.

Heuristic Commits—The number of transactions for which the resource reported a heuristic commit.

Heuristic Rollbacks—The number of transactions for which the resource reported a heuristic rollback.

Mixed Heuristics—The number of transactions for which the resource reported a mixed heuristic decision. In a mixed heuristic decision, the Transaction Manager is aware that a transaction resulted in a mixed outcome, where some participating resources committed and some rolled back.

Heuristic Hazards—The number of transactions for which the resource reported a heuristic hazard decision. In a heuristic hazard decision, the Transaction Manager is aware that a transaction might have resulted in a mixed outcome, where some participating resources committed and some rolled back, but system or resource failures make it impossible to know for sure whether a heuristic mixed outcome definitely occurred.