Transaction
The SAP J2EE Engine enables distributed transactions which can spread over many different resources and even pass the boundaries of an application.
The monitoring group contains the following important monitors that are activated by default:
● ActiveTransactionsCount
Description of monitor |
The number of JTA transactions that are currently open. |
Description of possible problems and their impact |
If value is greater than 500 or if there are timed out transactions, it means that the user load is too high or errors are preventing the transactions from completing. The open transactions number is closely related to the number of used connections – if there are a lot of open transactions, probably the connection pool is going to get exhausted, and vice versa – if the pool got exhausted the open transactions can increase a lot. There can also be other errors that are causing the problem. |
Boundary conditions for the metric (thresholds) |
We recommend you set the following: GY 500 YR 2147483647 RY 2147483647 YG 500 |
Recommended procedure if a problem occurs |
Check the log file size increment. If it has increased in size recently, this can mean that a lot of errors are reported. In this case, check the logs to analyze the cause for the errors. Read SAP Note 719778 and make a full thread dump to narrow the suspicious code. |
● CommittedTransactionsCount
Description of monitor |
This is an aggregated number of transactions that have been committed. |
Description of possible problems and their impact |
Does not indicate a problem. |
Boundary conditions for the metric (thresholds) |
We recommend you set the following: GY 2147483646 YR 2147483647 RY 2147483647 YG 2147483646 |
Recommended procedure if a problem occurs |
Does not indicate a problem. |
● RolledBackTransactionsCount
Description of monitor |
This is an aggregated number of transactions that have been rolled back. |
Description of possible problems and their impact |
Does not indicate a problem. |
Boundary conditions for the metric (thresholds) |
We recommend to set the following: GY 2147483646 YR 2147483647 RY 2147483647 YG 2147483646 |
Recommended procedure if a problem occurs |
Does not indicate a problem. |
● TransactionsSuccessRate
Description of monitor |
This is the ratio in percentage between committed and completed transactions - (CommittedTransactionsCount*100)/ (CommittedTransactionsCount+ RolledBackTransactionsCount). |
Description of possible problems and their impact |
The target value is 99, 99999%. If the value is less than 90 then there are many transactions that fail, which means that either a lot of users have canceled transactions (a possible scenario), or some errors are preventing the transactions from committing successfully. |
Boundary conditions for the metric (thresholds) |
We recommend you set the following: GY 100 YR 101 RY 101 YG 100 |
Recommended procedure if a problem occurs |
Check the log file size increment. If it has increased in size recently, then this can mean that a lot of errors are reported. In this case, check the logs to analyze the causes for the errors. |
● TimedOutTransactionsCount
Description of monitor |
This is an aggregated number of transactions that have timed out. |
Description of possible problems and their impact |
If the timed out transactions count is greater than 1 or if it has increased recently, it can be an indication that errors are preventing the transactions from completing or the specified transaction timeout is not adequate to the user load. |
Boundary conditions for the metric (thresholds) |
We recommend you set the following: GY 1 YR 2147483647 RY 2147483647 YG 1 |
Recommended procedure if a problem occurs |
Check the log file size increment. If it has increased in size recently, then this can mean that a lot of errors are reported. In this case, check the logs to analyze the cause for the errors. Read SAP Note 719778 and make a full thread dump to narrow the suspicious code. |