Introscope report MQ errors

Document ID : KB000101597
Last Modified Date : 15/06/2018
Show Technical Document Details
Issue:


Customer has deployed Introscope 10.5 agent on Websphere Liberty JVMs. JVMs do not make MQ calls and they have not configured Introscope to monitor MQ but Introscope kept reporting MQ errors on the Application Logs.
But NO MQMonitoring is enabled.

[err] java.lang.ClassNotFoundException: com.wily.powerpack.websphereMQ.agent.extensions.tracer.hc2.MQBackendTracer
[err] at java.lang.Class.forNameImpl(Native Method)
[err] at [internal classes]
[err] at com.wily.introscope.agent.trace.TracerAdministrator.access$0(TracerAdministrator.java:649)
[err] at com.wily.introscope.agent.trace.TracerAdministrator$ProbeInformationCreator.IProbeInformationCreator_createProbeInformation(TracerAdministrator.java:806)
[err] at [internal classes]
[err] java.lang.ClassNotFoundException: com.wily.powerpack.websphereMQ.agent.extensions.tracer.hc2.MQBackendTracer
[err] at java.lang.Class.forNameImpl(Native Method)
[err] at [internal classes]
Environment:
Release 10.5.1.8
Websphere Liberty profile
OpenShift Docker
No Duplicate Agent Instance.
The App doesn't make MQ calls.
Disabled MQ monitoring from Introscope.
No MQMonitor was set
Cause:

Unfortunately, the Agent profile is used from another OpenShift Docker Container Agent Profile
As per the IntroscopeAgent Log:
  • 5/31/18 06:13:44 PM EDT [INFO] [IntroscopeAgent.Properties] introscope.autoprobe.directivesFile=websphere-typical.pbl,webspheremq.pbl,hotdeploy,
Resolution:

Make sure the correct Agent is configured with out WebshpereMQ.pbd or webspheremq_extra.pbd  or webspheremq.pbl specified for Directives Files