HornetQ Monitoring: Difference between revisions
Jump to navigation
Jump to search
Line 34: | Line 34: | ||
====messageCount==== | ====messageCount==== | ||
In case of a clustered destination, 'messageCount' refers to the number of messages stored in the ''local queue''. It is not a cluster-wide metric. | |||
====deliveringCount==== | ====deliveringCount==== | ||
====scheduledCount==== | ====scheduledCount==== |
Revision as of 21:27, 1 June 2017
Internal
Relevance
- EAP 6.4.10
JMX Monitoring
jboss.as:subsystem=messaging,hornetq-server=default
Destinations
All deployed JMS destination, Dead Letter Queues and Expiry Queues can be monitored over JMX. The deployed destination ObjectName pattern is:
jboss.as:subsystem=messaging,hornetq-server=default,jms-queue=<queue-name>
Dead Letter Queue ObjectName:
jboss.as:subsystem=messaging,hornetq-server=default,jms-queue=DLQ
ExpiryQueue ObjectName:
jboss.as:subsystem=messaging,hornetq-server=default,jms-queue=ExpiryQueue
JMX Attributes
messageCount
In case of a clustered destination, 'messageCount' refers to the number of messages stored in the local queue. It is not a cluster-wide metric.
deliveringCount
scheduledCount
messageAdded
consumerCount
The number of JMS consumers currently associated and consuming messages from this destination.