HornetQ Monitoring: Difference between revisions
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
==Destinations== | ==Destinations== | ||
All deployed JMS destination, Dead Letter Queues and Expiry Queues can be monitored over JMX. The deployed destination ObjectName pattern is: | |||
=== | <pre> | ||
jboss.as:subsystem=messaging,hornetq-server=default,jms-queue=<queue-name> | |||
</pre> | |||
Dead Letter Queue ObjectName: | |||
<pre> | |||
jboss.as:subsystem=messaging,hornetq-server=default,jms-queue=DLQ | |||
</pre> | |||
ExpiryQueue ObjectName: | |||
=== | <pre> | ||
jboss.as:subsystem=messaging,hornetq-server=default,jms-queue=ExpiryQueue | |||
</pre> | |||
=== | ===JMX Attributes=== | ||
====messageCount==== | ====messageCount==== | ||
====deliveringCount==== | |||
====scheduledCount==== | |||
====messageAdded==== | |||
====consumerCount==== | |||
The number of JMS consumers currently associated and consuming messages from this destination. | |||
==== | ====entries==== | ||
===JMX Operations=== | ===JMX Operations=== | ||
Revision as of 15:29, 11 May 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
deliveringCount
scheduledCount
messageAdded
consumerCount
The number of JMS consumers currently associated and consuming messages from this destination.