Smart Plug-in for WebLogic Server Reference Guide

1-64
Chapter 1
Metric B077_TranHeurCnt
Instruction text (contd.) HeuristicCommit - one resource participating in a transaction decided to
autonomously commit its work, even though it agreed to prepare itself and wait
for a commit decision. If the Transaction Manager decided to rollback the
transaction, the resource's heuristic commit decision was incorrect, and might
lead to an inconsistent outcome since other branches of the transaction were
rolled back.
HeuristicMixed - the Transaction Manager is aware that a transaction resulted in
a mixed outcome, where some participating resources committed and some
rolled back. The underlying cause was most likely heuristic rollback or heuristic
commit decisions made by one or more of the participating resources.
HeuristicHazard - 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. The underlying cause was most likely heuristic rollback or heuristic
commit decisions made by one or more of the participating resources.
When a heuristic completion occurs, a message is written to the server log.
Refer to your database vendor documentation for instructions on resolving
heuristic completions.
Some resource managers save context information for heuristic completions.
This information can be helpful in resolving resource manager data
inconsistencies. If the ForgetHeuristics attribute is selected (set to true) on the
JTA panel of the WebLogic Console, this information is removed after an
heuristic completion. When using a resource manager that saves context
information, you may want to set the ForgetHeuristics attribute to false.
Action Operator-initiated graph; Application Bank Report (ASCII report)
Area Transactions
Monitor Template Name WLSSPI_0077