MQ correlation header insertion persisted with MQ Power Pack disabled

Document ID : KB000095774
Last Modified Date : 22/05/2018
Show Technical Document Details
Issue:
We have an issue where the MQ power pack agent is producing significant overhead with MQ transactions hence we have disabled the power pack whilst further testing occurs. However, slowness is still occurring without MQ Power Pack, and has now been traced to the correlation ID being injected. Performance Testing has been performed with / without agent to confirm this  and the only changed component observed in MQ Broker is the additional correlation ID when the Introscope Java agent is enabled.

Following properties had been added to the IntroscopeAgent.profile, however, the correlation ID is still being injected:

com.wily.introscope.agent.mqheaderinsertion.enabled=false
com.wily.introscope.agent.mqheaderread.enabled=false


This is causing significant slowness to the application. We need to understand how to stop the MQ correlation ID from being inserted
Environment:
CA APM Introscope Java Agent for WebSphere Application Server 10.5.2.10

 
Cause:
Upon investigation, the header inserted was:

<usr><CA_APM_CorID>4D0489950A34C1923B0C9195E3938311,1:1,0,0,,,AgAAAVVIQgAAAAFGAAAAAQAAABFqYXZhLnV0aWwuSGFzaE1hcAAAAARI
QgAAAAJGAAAAAgAAABBqYXZhLmxhbmcuU3RyaW5nAApUeG5UcmFjZUlkSEIAAAADRQAAAAIAJDRDRjE0QzVGMEEzNEMxOTIzQjBDOTE5NTIyQz
MwMkVDOTU0M0hCAAAABEUAAAACABNDYWxsZXIgQ29tcG9uZW50IElESEIAAAAFRQAAAAIAATFIQgAAAAZFAAAAAgAPQ2FsbGVyVGltZXN0YW1w
SEIAAAAHRQAAAAIADTE1MjYwMDU1MzMwNzdIQgAAAAhFAAAAAgARVXBzdHJlYW1HVUlEQ2FjaGVIQgAAAAlGAAAAAwAAABNqYXZhLnV0aWwuQX
JyYXlMaXN0AAAAAUhCAAAACkUAAAACACA0RDAyMTIyOTBBMzRDMTkyM0IwQzkxOTUxMzdENzQxMg==</CA_APM_CorID></usr>

<CA_APM_CorID> refers to JMS Correlation header inserted by JMS monitoring through jms.pbd.
Resolution:
To disable core agent JMS Correlation header insertion, please disable the following tracer in the jms.pbd file.

You can either:

1. Comment out the TurnOn: JMSCorrelationTracing. For example:

#TurnOn: JMSCorrelationTracing

or

2. Use the TurnOff switch. For example:

TurnOff: JMSCorrelationTracing

An agent restart is required for the changes to take effect.

 
Additional Information:
The method discussed in the following KB article is only applicable for SOA Extension for TIBCO EMS:
Lengthy JMS header injection seen in TIBCO EMS/JMS messages.