IV55794: WMQ 7.1.0.2: APPLICATION USING MQ CLASSES FOR JMS FAILS TO SEND MESSAGES WHEN MAXMSGL(0) IN CCDT, RC 2010

Fix Pack 7.1.0.5 for WebSphere MQ V7.1
WebSphere MQ V7.5 Fix Pack 7.5.0.4

APAR status

• Closed as program error.

Error description

• Application using WebSphere MQ classes for JMS fails to send
  messages when MAXMSGL(0) in CCDT, getting RC 2010
  ('MQRC_DATA_LENGTH_ERROR').
  
  Scenario 1. set MAXMSGL(0) in CCDT, JMS application (for
  example, WebLogic) fails with RC2010 when sending a 300KB
  message.
  Scenario 2. set MAXMSGL(4194304) in CCDT, which is the default
  size of 4 MB, JMS application succeeds when sending the same
  message.
  
  The exception java stack looks as following:
  
  com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed
  with compcode '2' ('MQCC_FAILED') reason '2010'
  ('MQRC_DATA_LENGTH_ERROR').
  com.ibm.msg.client.wmq.common.internal.Reason.createException(Re
  ason.java:204)
  com.ibm.msg.client.wmq.internal.WMQMessageProducer.checkJmqiCall
  Success(WMQMessageProducer.java:1056)
  com.ibm.msg.client.wmq.internal.WMQMessageProducer.checkJmqiCall
  Success(WMQMessageProducer.java:1014)
  com.ibm.msg.client.wmq.internal.WMQMessageProducer.access$800(WM
  QMessageProducer.java:63)
  com.ibm.msg.client.wmq.internal.WMQMessageProducer$SpiIdentified
  ProducerShadow.sendInternal(WMQMessageProducer.java:814)
  com.ibm.msg.client.wmq.internal.WMQMessageProducer$ProducerShado
  w.send(WMQMessageProducer.java:526)
  com.ibm.msg.client.wmq.internal.WMQMessageProducer.send(WMQMessa
  geProducer.java:1173)
  com.ibm.msg.client.jms.internal.JmsMessageProducerImpl.sendMessa
  ge(JmsMessageProducerImpl.java:925)
  com.ibm.msg.client.jms.internal.JmsMessageProducerImpl.send_(Jms
  MessageProducerImpl.java:781)
  com.ibm.msg.client.jms.internal.JmsMessageProducerImpl.send(JmsM
  essageProducerImpl.java:444)
  com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:296
  )
  com.ibm.mq.connector.outbound.MessageProducerWrapper.send(Messag
  eProducerWrapper.java:221)
  

Local fix

• Set the MAXMSGL property in the CCDT (maximum message length) to
  a valid non-zero value. For example, MAXMSGL(4194304), which
  is the default value of 4 MB.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This APAR affects all users of the WebSphere MQ classes for
  JMS who use a CCDT with a CLNTCONN channel that has the
  MAXMSGL attribute set to zero.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM SUMMARY:
  When the WebSphere MQ classes for JMS application attempted to
  connect to a Queue Manager, via a CCDT, using a CLNTCONN channel
  with MAXMSGL set to zero, the zero length was incorrectly
  taken to be the desired maximum message size. This meant that no
  messages were sent to the Queue Manager and a 2010
  ('MQRC_DATA_LENGTH_ERROR') return code was presented to the
  application for each message.
  

Problem conclusion

• The WebSphere MQ classes for JMS have been modified to correctly
  process the MAXMSGL attribute on the CLNTCONN channel definition
  when it has been set to zero. A MAXMSGL value of 0 will use the
  MAXMSGL attribute setting from the Queue Manager, as described
  by the product documentation.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.1       7.1.0.5
  v7.5       7.5.0.4
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WMQ AIX V7

• Fixed component ID

  5724H7221

Applicable component levels

• R710 PSY

     UP