Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Configuring Qpid JMX Management Console

Qpid has a JMX management interface that exposes a number of components of the running broker.
You can find out more about the features exposed by the JMX interfaces here.

Anchor
eclipsercp
eclipsercp

Installing the Qpid JMX Management Console

  1. Unzip the archive to a suitable location.
    Info
    titleSSL encrypted connections

    Recent versions of the broker can make use of SSL to encrypt their RMI based JMX connections. If a broker being connected to is making use of this ability then additional console configuration may be required, particularly when using self-signed certificates. See Management Console Security for details.

Info
titleJMXMP based connections

In previous releases of Qpid (M4 and below) the broker JMX connections could make use of the JMXMPConnector for additional security over its default RMI based JMX configuration. This is no longer the case, with SSL encrypted RMI being the favored approach going forward. However, if you wish to connect to an older broker using JMXMP the console will support this so long as the jmxremote_optional.jar file is provided to it. For details see Management Console Security.

Running the Qpid JMX Management Console

The console can be started in the following way, depending on platform:

...

  • Mac OS X: by launching the consoles application bundle (.app file).

Using the Qpid JMX Management Console

Please see Qpid JMX Management Console User Guide for details on using this Eclipse RCP application. The guide contains some screenshots of the Qpid JMX Management Console and an description of what the features are.

Anchor
jconsole
jconsole

Using JConsole

JConsole is a management tool that comes with the Java Runtime Environment (6+) or Java Development Kit (5+) and provides a very simple view of managed beans. It requires no special configuration to be used with Qpid.
You can run JConsole with the command 'jconsole' assuming you have Java installed and configured to be available in your PATH.

...

titleSSL encrypted connections

...

See

...

To attach to a running broker simply enter the host, port, and login details in the JConsole connect dialog.
Once you are connected expand the tree nodes marked "org.apache.qpid" to gain access to the Qpid related MBeans.For further details see Sun's JConsole guide
Please see attachment for some of the screenshots of using jconsole for Qpid.

Anchor
hermesjms
hermesjms

Using HermesJMS

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

Using MC4J

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

Installation

  • First download and install MC4J for your platform. Version 1.2 beta 9 is the latest version that has been tested.
  • Copy the directory blaze/java/management/mc4j into the directory <MC4J-Installation>/dashboards

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

You can view tabular summaries of the queues, exchanges and connections using the Global Dashboards->QPID tree view. To drill down on individual beans you can right click on the bean. This will show any available graphs too.