After upgrading the java agent for 126.96.36.199 to 10.5.2, we are seeing a new tag <CA_APM_CorID> getting injected in the application header which is causing issues? Does anyone know how to disable this?
If this is due to standard SPM/SOA correlation these properties should stop it:
com.wily.introscope.agent.soapheaderread.enabled=false com.wily.introscope.agent.soapheaderinsertion.enabled=false com.wily.introscope.agent.httpheaderread.enabled=false com.wily.introscope.agent.httpheaderinsertion.enabled=false
SOA-Specific Agent Configuration Properties - CA Application Performance Management - 10.5 - CA Technologies Documentati…
If that does not change the behaviour it may be related to redesigned HTTP correlation in 10.x which no longer needs SPM/SOA extension and is enabled by default. You can try to comment out httpcorrelation.pbd in the *typical.pbl/*full.pbl file you are using and see if that makes any difference.
Hope that helps
FYI on the ID -- What are names of the headers used for cross correlation traces?
I wonder if this is related to JMS correlation, believe Http and JMS correlation mechanism work independently.
If you are using Tibco, OSB and Webmethods, we have the below property.com.wily.introscope.agent.jmsheaderinsertion.enabled
Try to removing jms.pbd from the <app>-full/typical pbl
I hope this helps,
Two possible solutions were given. So marking as correct.
However, the thread does not have to end here. Please let us know if any of the recommendations helped resolve the issue. And if you have any followup questions.
Retrieving data ...