Seeing a flood of "[WARN] [IntroscopeAgent.MQNameFormatter] CAMQ7QueueSender:getQueueName:Exception:com.ibm.msg.client.wmq.v6.jms.internal.MQXASession.getQM() messages."

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

  Seeing hundreds of the following message in the Agent Log:

 [WARN] [IntroscopeAgent.MQNameFormatter] CAMQ7QueueSender:getQueueName:Exception:com.ibm.msg.client.wmq.v6.jms.internal.MQXASession.getQM() 

 

Also seeing an Unknown Queue Manager message in the Investigator

 

And seeing in the same logs:

[WARN] [IntroscopeAgent.Agent] Dynamic Instrumentation is turned off 

[WARN] [IntroscopeAgent.BoundaryDetection] Automatic Boundary Detection Service is turned off because DI is not supported. 

[WARN] [IntroscopeAgent.MQNameFormatter] MQClassLoaderUtil.loadJMSClasses(ClassLoader) JMS Class Loading: Ignore for MQ7.x: propertiesReadOnly. Make 

[WARN] [IntroscopeAgent.Agent] handshake.mqagent.id value is blank or not a number. This is mandatory property for MQ trace. Handshake will not be started without valid value.

Environment:
All Supported APM Releases
Cause:

The warnings are because of not having the required jars in the classpath of the application server.  These jar files must be of the same version.  Generally during an upgrade these jars are upgraded, however if this was upgraded manually, you must ensure that the jars in the "core/ext" directory are upgraded as well.

 

Resolution:

1. Add the required jars in the classpath of the application server.  If this was manually upgraded, ensure you are using the correct version of the jar files.

 

Workarounds: 

1. Here is how to suppress the error and still get all metrics. 

You would need to add the following at the end of the logging section or even at the very bottom of the profile: 

log4j.logger.IntroscopeAgent.MQNameFormatter=ERROR, logfile 

 

You will then only get ERROR and FATAL messages from that agent component in the log and the WARNings will no longer appear. 

Normally there is no need to restart the application for the logging changes to take effect but adding a new property will require to restart the application for the changes to take effect. 

 

 - OR -

2. Tentatively commenting out the following tracer in the pbd to avoid triggering the repeated exception messages in agent logs.  This would require a restart of the Agent.

 

#TurnOn:MQJMSmqQueueSender

 

Additional Information: