We had some SOAP messages rejected due to the fact APM agent is inserting correlation id on SOAP.
We found it's the APM agent and applied below four properties to profile file. But even after we applied, the messages are being injected with correlation id and failed again. The app server restart was done so changes went on effect.
Also when I tried to check for traces, I can see cross-process data id for tracers. If I disabled it via profile, how the tracers are still appearing with cross-process data(correlation id). Is there anything else forcefully inserting from agent code? or EM?
I would like to understand why is it behaving in this way.