Page History

...

Qpid JMX Management

...

QPID has a management interface that exposes. By default the management interface is enabled but it can also be disabled by modifying the management element in config.xml.

When starting the broker, the following system properties need to be set by setting the environment variable QPID_OPTS:

You can find out more about the features exposed by the Qpid JMS interfaces here.

Using JConsole

JConsole is a management tool that comes with the Java Runtime Environment and provides a very simple view of managed beans. It requires no special configuration to be used with QPID.

To attach to a running broker simply enter the host and port details on the JConsole connect dialog. The port should be the same as the one specified in the system property com.sun.management.jmxremote.port.

Once you are connected expand the tree nodes marked "org.apache".

Please see attachment for some of the screenshots of using jconsole for Qpid.

Using HermesJMS

HermesJMS also offers integration with the Qpid management interfaces. You can get instructions and more information from http://cwiki.apache.org/confluence/display/qpid/HermesJMS

Using MC4J

MC4J is an alternative management tool. It provide a richer "dashboard" that can customise the raw MBeans.

Installation

TBC - needs updated with current instructions

• First download and install MC4J for your platform. Version 1.2 beta 9 is the latest version that has been tested.
• Copy the directory XXX into the directory XXX

Configuration

You should create a connection the JVM to be managed. Using the Management->Create Server Connection menu option. The connection URL should be of the form: service:jmx:rmi:///jndi/rmi://localhost:8999/jmxrmi making the appropriate host and post changes.

Operation

...

Console

Overview

The Qpid JMX Management Console is a standalone Eclipse RCP application that communicates with the broker using JMX.