JMX Monitoring and Management Console: Frequently Asked Questions

There are some frequently asked questions about the JMX Monitoring and Management Console such how it is used to monitor JMS 1.1 Pools or how to use the JMX to monitor JMS 1.1 Async Recevie adapters.

How can I use the JMX to monitor JMS 1.1 Pools?

You can use the JMX to monitor pools created by the Dynamic Class Loading or Custom Class Loading. The JMS 1.1 exposes the Monitor and Segmented Pool Monitor MBeans. The JMX supports the following pool operations:
Pool Operation Description/Usage
listPools Lists all the JMS pools created. If the same operation is selected from Segmented Pool Monitor, it lists all the pools created using Custom Class Loading.
stopPool Used to shutdown any pool by providing the pool name. This can be used in addition to shutting down pools from JMS 1.1 Release Connection and Session service.
getPoolDetails Used to get more information about the pool by providing the pool name.

How is JMX helpful in dealing with Request Reply when using Permanent Destination mode?

JMS 1.1 Request Reply service uses an async receiver when used in Permanent Destination mode. When used in Permanent Destination mode, the JMS 1.1 Request Reply Service exposes an MBean for monitoring various parameters. The following JMX operations can be useful in monitoring the JMS 1.1 Request Reply Service:
JMX Operations Description/Usage
listContainers A new async receiver is created when using JMS 1.1 Request Reply Service in Permanent Destination mode, when certain parameters are changed. These various async receivers are known as containers and can be seen from either the drop down in JMS 1.1 Release Connection and Session service or by invoking this method.
stopContainer If you want to stop any of these async receivers, you can do this by providing the container name and invoking the stopContainer method. This can also be achieved by using the JMS 1.1 Release Connection and Session service.
pendingRequestCount If you want to know the number of requests that are awaiting replies. If the Permanent Destination mode is the same destination used to receive replies for every request, replies are marked pending until the time a reply is received.
pendingRequestCorrelationIDs If you want to know correlation IDs for the pending requests.

How can I use the JMX to monitor JMS 1.1 Async Receive adapters?

The JMX can be used to listen for notifications sent by JMS 1.1 Async Receive adapters. If the retry is specified for JMS 1.1 Async Receive adapter and if an adapter goes down, then the JMX notifications are broadcast and can be subscribed to.

What is that Destination Monitor I see in JMX screen?

MBeans can be used to monitor all the destinations cached by various JMS 1.1 services. If you are using the JNDI lookup for destinations, then the destinations are cached to avoid the JNDI lookup every time. If needed, these destinations can be cleared from the cache using this MBean.

Note: JMX monitoring of IBM B2B Integrator can only be done with the events that are currently output by the framework. There is no framework to output additional events.