Getting MQRC_PROPERTIES_TOO_BIG errors in WebSphereMQ JVM log (SystemOut.log)

Products

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

Issue/Introduction

Description:

After upgrading the introscope agent to Version 91XX on WebSphereMQ, we see the following errors in WebSphereMQ JVM log (SystemOut.log):

ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource JMS$XXXXXXMQConnectionFactory_XXX$JMSManagedConnection@33. The exception is: com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ2007: Failed to send a message to destination 'CTCS.THN.ARCHIVE.RESPONSE'. JMS attempted to perform an MQPUT or MQPUT1; however WebSphere MQ reported an error. Use the linked exception to determine the cause of this error.:com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2478' ('MQRC_PROPERTIES_TOO_BIG').

ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource jms/XXXXXMQConnectionFactory_XXX. The exception is: com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ2007: Failed to send a message to destination 'CTCS.THN.ARCHIVE.RESPONSE'. JMS attempted to perform an MQPUT or MQPUT1; however WebSphere MQ reported an error. Use the linked exception to determine the cause of this error.:com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('JMSWMQ2007:) reason '2478' ('MQRC_PROPERTIES_TOO_BIG').

Environment

Release:
Component: APMAGT

Resolution

Solution:

Please take the following steps in this case to see if the problem gets corrected:

1. Set the following properties in introscope agent properties file (IntroscopeAgent.profile):
   
   introscope.agent.websphere.crossjvm=false
   introscope.agent.crossprocess.correlationid.maxlimit=256
   Recycle the WebSphereMQ JVM and check if the problem gets corrected.
   
   If you continue to observe the same problem, please take these additional steps:
   
   
2. Set the following properties in MQAgent properties file (MQAgent.properties)
   
   mq.crossprocesstracing.enabled = false
   mq.sysviewtracing.enabled = false
   Recycle the WebSphereMQ JVM and check if the problem gets corrected.
   
   If you continue to observe the same problem, please take following additional steps:
   
   
3. Disable WPS.pbd/wps.pbd:
   
   Review the Introscope AutoProbe Log and check if the WPS.pbd/wps.pbd is enabled. If this PBD is enabled, please disable this PBD (comment out this PBD, so that it cannot be used to instrument the agent).
   
   Recycle the WebSphereMQ JVM and check if the problem gets corrected.
   
   Please also confirm if the above mentioned PBD is properly disabled by reviewing the Introscope AutoProbe Log.