HornetQ Monitoring

Internal

• WildFly Monitoring

Relevance

• EAP 6.4.10

JMX Monitoring

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.

consumerCount

The number of JMS consumers currently associated and consuming messages from this destination.