Resource MBeans

Resource MBeans are associated with individual Message Queue resources of the following types:

• Message brokers

• Connection services

• Connections

• Destinations

• Broker clusters

• Logging

• The Java Virtual Machine (JVM)

Configuration and monitoring functions are implemented by separate MBeans. Each managed resource is associated with a configuration MBean for setting the resource's configuration and a monitor MBean for gathering (typically transient) information about its runtime state. For instance, there is a destination configuration MBean for configuring a destination and a destination monitor MBean for obtaining runtime information about it. In general, each instance of a managed resource has its own pair of MBeans: thus there is a separate destination configuration MBean and destination monitor MBean for each individual destination. (In the case of the Java Virtual Machine, there is only a JVM monitor MBean with no corresponding configuration MBean.)

Configuration MBeans are used to perform such tasks as the following:

• Set a broker's port number

• Set a broker's maximum message size

• Pause a connection service

• Set the maximum number of threads for a connection service

• Purge all messages from a destination

• Set the level of logging information to be written to an output channel

Monitor MBeans are used to obtain runtime information such as the following:

• The current number of connections on a service

• The cumulative number of messages received by a destination since the broker was started

• The current state (running or paused) of a queue destination

• The current number of message producers for a topic destination

• The host name and port number of a cluster's master broker

• The current JVM heap size