For java - MQ tracing , we turn on tracing in MQAgent.properties, which is one of the many steps. By default , MQ header insertion and read are enabled. This always created issues in customers applications as they dont allow any changes in mq header.
How are we supposed to do this then? I believe none of the customers allow such changes?
Yes, by default the header insertion is On and customers can turn it OffBased on my research, I am not sure all the customers have problem with thatDoes he want the default value to be false? In that case, transaction trace might get disturbed, from https://docops.ca.com/ca-apm/10-5/en/extending/ibm-websphere-mq/mqagent-properties-file#MQAgent.propertiesFile-mq.headerinsertion.enabled
mq.headerinsertion.enabledThis property is used to enable MQRFH2 or JMS header insertion which is ***needed for correlating MQ Connector calls with other Java Components. ***
Thanks for reply.
None of my customers allow anything to be added in their mq header as part of message validation in their application process flow. The message recipients will just reject those messages and then the applications would start behaving abnormal.
So we set those properties to false.
I wonder how other customers are, whether they allow additional parameters in their mq header . I want to know industry wide standard practice.
If anyone has done, please share how these were configured?
Hi Geethu,If you have MQ JMS Application – you can disable header insertion and use 10.3 + Agent which has JMS correlation support, see CA APM Release Notes - CA Application Performance Management - 10.3 - CA Technologies Documentation
Was your question answered by Sergio?
It looks like Sergio has answered your question so marking as correct. Your response is more of a nature of a discussion. I hope that you and others continue this important discussion on mq headers