MQ traces not visible in MQMonitor Agent

Document ID : KB000007526
Last Modified Date : 14/02/2018
Show Technical Document Details

MQ Traces were not visible after configuring MQMonitor agent as required.

We are getting the following error when MQ transactions are being executed:

Exception in thread "<QUEUE_NAME>|<host-name>" java.lang.NoSuchMethodError: method <init>()V not found
at com.wily.powerpack.websphereMQ.agent.MQMonitor.trace.ActivityReportParser.parseActivityMessage(
at com.wily.powerpack.websphereMQ.agent.MQMonitor.trace.ActivityReportParser.parseMessage(
at com.wily.powerpack.websphereMQ.agent.MQMonitor.trace.ActivityReportParser.getActivityReportTransaction(
at com.wily.powerpack.websphereMQ.agent.MQMonitor.trace.QueueBrowserUtil.mqReadActivityMessage(

CA Application Performance Management with IBM Websphere MQ Extension

The exception indicates that the which is required for MQ traces on MQMonitor side, is either missing or not configured in the correct order in the classpath.


1. If MQMonitor is started using the  startup script (startMQMonitor.bat (Windows) or (UNIX)):

a) Add in the beginning of the list of MQ jars in the CLASSPATH of the startMQMonitor.bat file.

For example:
set CLASSPATH=MQMonitor.jar;.\lib\Agent.jar;.\lib\jline-0.9.94.jar;.\lib\;.\lib\;.\lib\;.\lib\connector.jar;.\lib\;.\lib\dhbcore.jar;.\lib\;.\lib\;.\lib\;.\lib\j2ee.jar;.\lib\ibmjsseprovider2.jar;.\lib\ConfigManagerProxy.jar
b) Make sure the file is copied to/present in the defined path.
c) Restart the MQMonitor

2. If MQMonitor is started as a Windows Service:

a) Add the into the classpath in the wrapper.conf file, in exactly the following order ( must come before :

b) Make sure the file is copied to/present in the defined path.
c) Restart the MQMonitor service


Additional Information:

IBM WebSphere MQ Extension