Information about JMS property X_Mercury_Diag_Color added to the MQ message

Messages in MQ have an extra JMS property X_Mercury_Diag_Color added to it when diagnostics is enabled. This will cause issues in message handling components.

HP Diagnostics need the JMS property X_Mercury_Diag_Color to for JMS cross-vm outbound calls and topology. It’s not intended to interfere with the application unless the app monitor the custom JMS property.

It is inserted by the following points’ code snippets.

[JMS-QueueSender1]

[JMS-QueueSender2]

[JMS-TopicPublisher1]

[JMS-TopicPublisher2]

User can either disable the points entirely, or just the detail section to block the code snippets.

However please note that disabling these points reduces diagnostics functionality, in particular, cross-vm correlations between the applications communication via JMS. Therefore should only disable these as a last work around, AND only disable for the specific probes that send JMS messages to recipients that fail.

A better workaround will be to ignore the JMSMessage properties that are not recognizable in the application. Example: to review/check how the application handles the JMS property, and see if it is possible to change the logic or add a filter to ignore the JMS property X_Mercury_Diag_Color (or to ignore any unknown JMS properties).

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s