WildFly Transaction Manager Monitoring: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
(Created page with "=Internal= * WildFly Monitoring =Activation= Statistics must be explicitly enabled. =JMX Monitoring=")
 
 
(2 intermediate revisions by the same user not shown)
Line 2: Line 2:


* [[WildFly Monitoring#Metrics|WildFly Monitoring]]
* [[WildFly Monitoring#Metrics|WildFly Monitoring]]
=Relevance=
* EAP 6.4.10


=Activation=
=Activation=
Line 8: Line 12:


=JMX Monitoring=
=JMX Monitoring=
JTA transaction statistics can be collected from the JBoss “transactions” subsystem, using the following JMX ObjectName:
<pre>
jboss.as:subsystem=transactions
</pre>
The following JMX attributes are available:
==JMX Attributes==
====numberOfTransactions====
====numberOfAbortedTransactions====
====numberOfApplicationRollbacks====
====numberOfCommittedTransactions====
====numberOfHeuristics====
====numberOfInflightTransactions====
====numberOfNestedTransactions====
====numberOfResourceRollbacks====
====numberOfTimedOutTransactions====

Latest revision as of 15:52, 11 May 2017

Internal

Relevance

  • EAP 6.4.10

Activation

Statistics must be explicitly enabled.

JMX Monitoring

JTA transaction statistics can be collected from the JBoss “transactions” subsystem, using the following JMX ObjectName:

jboss.as:subsystem=transactions

The following JMX attributes are available:

JMX Attributes

numberOfTransactions

numberOfAbortedTransactions

numberOfApplicationRollbacks

numberOfCommittedTransactions

numberOfHeuristics

numberOfInflightTransactions

numberOfNestedTransactions

numberOfResourceRollbacks

numberOfTimedOutTransactions