ActiveMQ inside Java Camel pulls excessive <CA_APM_CorID>

Products

• CA Application Performance Management Agent (APM / Wily / Introscope)
• CA Application Performance Management (APM / Wily / Introscope)
• INTROSCOPE
• DX Application Performance Management

Issue/Introduction

We have an EC2 Java 11.x agent inserting the headers on the same instance running ActiveMQ v5.14, blowing up the application. Basically ActiveMQ runs inside the Java Camel process. The client runs their MQ on a mainframe, and they have a hard limit of 1024 chars for the whole header so this correlation id from APM is stopping them from pulling any messages.

 This is what it does:

 

<usr>
    <BroadcomMsgID>4004144887</BroadcomMsgID>
    <BroadcomJMSStage>true</BroadcomJMSStage>
    <CA_APM_CorID>
        1C1019720A8C697D678040B31AEFA6D0,1:1,0,0,,,AgBBBAAASZGGGIQgAAAAFGAAAAAQAAABFqYXZhLnV0aWwuSGFzaE1hcAAAAARIQgAAAAJGAAAAAgAAABBqYXZhLmxhbmcuU3RyannayannaW5nAApUeG5UcmFjZUlkSEIAAAADRQAAAAIAIjFDMEZGQzEzMEE4QzY5N0Q2NzgwNDBCMzBBQzU4QkNFOTNIQgAAAARFAAAAAgATQ2FsbGVyIENvbXBvbmVudCBJREhCAAAABUUAAAACAAExSEINNNAAAAGRQAAAAIAD0potNhbGxlclRpbWVzdGFtcEhCAAAAB0UAAAACAA0xNTgxMDE4NzgyMDY2SEIAAAAIRQAAAAIAEVVwc3RyZWFtR1VJRENhY2hlSEIAAAAJRgAAAAMAAAATamF2YS51dGlsLkFycmF5TGlzdAAAAAAzzzHHh=
    </CA_APM_CorID>
    <XSLTFileName>file:C:/aserve/AMS/resources/xslt/swift/event/20022_outbound.xslt</XSLTFileName>
    <breadcrumbId>ID-EC2AMAZ-M4UEM0Q-1581005878264-0-10757</breadcrumbId>
    <UserId>EVENT_OUTBOUND.schedule.Broadcom</UserId>
    <MessageTag dt='i8'>17840796</MessageTag>
    <MessageType>EventMessage</MessageType>
</usr>

 

Can we turn it off and where?

We have tried turning off header insertion properties and disabling correlation tracers , but the problem still persists:

in Introscopeagent.profile: 

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

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

setting :

introscope.agent.crossprocess.correlationid.maxlimit=512 

 

in jms.pbd

#TurnOn: JMSCorrelationTracing

 

Environment

Release : 11.1.0

Component : APM Agents

Cause

 The customer was using the default installation of Java agent for Windows downloaded from the DX APM SaaS portal that would include a list of commonly used agent extension bundles, including the Tibco agent extension that would enable JMSCorrelationTracing by default

Resolution

Download and deploy an agent installation specific to the applications (e.g Weblogic - below screenshot)  with the appropriate agent extensions selected and the tibco agent extension removed.