JTA

The JTA overview gives a quick access to the activity of JTA resource.

Transactions (unit)

Active Total count of active transactions. A consistently high value can indicate a heavy load on a server.

Rolledback (unit)

App

Total count of transactions that have rolledback due to the application calling setRollbackOnly or rollback explicitly.

A high value here can occur for any reason, but most often occurs due to some handled exception within an application, for example, SQLException during database update.

Suggest looking into application code which calls setRollbackOnly or rollback to see why it is doing so.

Admin

Total count of transactions that have rolledback due to administrative action.

A high value here suggests the system or application may not be automated enough. For example, too much system administration in general or inadequate handling of transaction architecture, or a particular issue has occurred which required extensive administration.

Resource

Total count of transactions that have rolledback due to and error in an enlisted resource.

A high value here can indicate an issue with one or more resource managers, for example, database or the network connection between OC4J and these resources.

TimedOut

Total count of transactions that have rolledback due to timeout.

A high number can indicate any number of issues are causing the transaction, or activity within transactional bounds, to take too long or the timeout value specified is not flexible enough.

Suggest looking into what activities within the transactions involved, which may be of a certain type or application, are taking up time or adjust the transaction-timeout value in the transaction-manager.xml configuration file.

Heuristic (unit)

Committed

Total count of heuristically committed transactions.

A high value suggests the system or application may not be automated enough, for example, too much system administration in general or inadequate handling of transaction architecture, or a particular issue has occurred which required extensive administration. This is due to a subordinate TransactionManager and not a resource manager being rollbacked while in the prepared state.

Rolledback

Total count of heuristically rolledback transactions.

A high value here suggests the system or application may not be automated enough for example, too much system administration in general or inadequate handling in transaction architecture, or a particular issue has occurred which required extensive administration. This is due to a subordinate TransactionManager and not a resource manager being committed while in the prepared state.

Exceptions (unit)

System

Total count of SystemExceptions encountered.

A high value here should never occur and indicates a serious failure in the system. Suggest analyzing OC4J and resource manager logs.

Security

Total count of SecurityExceptions encountered.

A high value, or any value getter than 0, can indicate an issue with the identity on the thread executing this.

Rollback

Total count of RollbackExceptions encountered.

A high value can indicate an issue in the system (for example, a database is down) which results in performance degradation. This can result from both a direct internal system failure or from the application calling setRollbackOnly for some reason.

Suggest examining the fine-grained rollback cause counts and logs for the cause of the rollbacks as well as looking into application code which calls setRollbackOnly.

Heuristic Rollback

Total count of HeuristicRollbackExceptions encountered.

A high value suggests the system or application may not be automated enough, for example, too much system administration in general or inadequate handling of transaction architecture, or a particular issue has occurred which required extensive administration. Unlike the rolledbackDueToAdminCount metric which indicates adminstrative rollback at the root transaction manager level while a transaction is active, this is due to either a subordinate TransactionManager or resource manager being rolledback while in the prepared state.

Heuristic Mixed

Total count of HeuristicMixedExceptions encountered.

A high value can indicate a high number of potentially non-ACID outcomes resulting from inconsistent or inappropriate administrative intervention.

Illegal State

Total count of IllegalStateExceptions encountered.

A high value should be rare and should only be possible as a result of prior administrative intervention.


See also:





Go back to the Learning center:


Copyright © AgileLoad. All rights reserved.
Agile Load testing tool| Contact AgileLoad | Terms of Use | Sitemap