IV32421: A VALUE OF 'NULL' FOR JMS PROPERTY JMSXGROUPSEQ IN WMQ V7 CAUSES 'NUMBERFORMATEXCEPTION' EXCEPTIONS.

WebSphere MQ V7.5 Fix Pack 7.5.0.1
WebSphere MQ V7.0 Fix Pack 7.0.1.10
Fix Pack 7.1.0.3 for WebSphere MQ V7.1

APAR status

• Closed as program error.

Error description

• When a WebSphere MQ client application using the WebSphere MQ
  classes for JMS sets the JMSX property JMSXGroupSeq to 'NULL',
  a NumberFormatException is thrown back to the client application
  and the message is not sent to the queue.
  
  Below is an example of what you may see in the application's
  log file:
  
  Sample stack trace:
  "java.lang.NumberFormatException: null
  at java.lang.Integer.parseInt(Integer.java:417)
  at java.lang.Integer.valueOf(Integer.java:554)
  at com.ibm.msg.client.wmq.common.internal.messages.
  WMQMessageProps.parseInt(WMQMessageProps.java:803)
  at com.ibm.msg.client.wmq.common.internal.messages.
  WMQMessageProps.getIntProperty(WMQMessageProps.java:418)
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of:
  
  - The WebSphere MQ V7.0.1 classes for JMS.
  - The WebSphere MQ V7.0.1 Resource Adapter.
  - The WebSphere MQ V7.1 classes for JMS.
  - The WebSphere MQ V7.1 Resource Adapter.
  - The WebSphere MQ V7.5 classes for JMS.
  - The WebSphere MQ V7.5 Resource Adapter.
  - The WebSphere Application Server V7 WebSphere MQ messaging
  provider.
  - The WebSphere Application Server V8.0 WebSphere MQ messaging
  provider.
  - The WebSphere Application Server V8.5 WebSphere MQ messaging
  provider.
  - The WebSphere Application Server V6.1 WebSphere MQ messaging
  provider who have configured the WebSphere variable
  MQ_INSTALL_ROOT to point to a WebSphere MQ V7.0 installation.
  - The WebSphere Application Server V6.1 WebSphere MQ messaging
  provider who have configured the WebSphere variable
  MQ_INSTALL_ROOT to point to a WebSphere MQ V7.1 installation.
  - The WebSphere Application Server V6.1 WebSphere MQ messaging
  provider who have configured the WebSphere variable
  MQ_INSTALL_ROOT to point to a WebSphere MQ V7.5 installation.
  
  who have JMS applications that connect to a WebSphere MQ
  V7.0.1, V7.1 or V7.5 queue manager using WebSphere MQ messaging
  provider normal mode, and then set the property JMSXGroupSeq to
  the value "null" on a JMS message before sending it.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
  ****************************************************************
  PROBLEM SUMMARY:
  When an application uses the WebSphere MQ classes for JMS
  (either stand-alone, as part of the WebSphere MQ Resource
  Adapter or as part of the WebSphere Application Server
  WebSphere MQ messaging provider) to send a JMS message, the
  WebSphere MQ classes for JMS will:
  
  - Construct a WebSphere MQ message.
  - Copy properties of the JMS message into properties of the
  WebSphere MQ message.
  - Copy the message body of the JMS message to the message body
  of the WebSphere MQ message.
  - Put the WebSphere MQ message to the WebSphere MQ queue that
  represents the JMS Destination the application is sending the
  message to.
  
  During the second step listed above, the WebSphere MQ classes
  for JMS checked to see if the JMXGroupSeq property had been
  defined on the JMS message. If it had, then the WebSphere MQ
  classes for JMS tried to convert the property value into an
  integer so that it could be copied into the MsgSeqNumber field
  in the MQMD of the WebSphere MQ message.
  
  Code changes were added to the WebSphere MQ V6 classes for JMS
  in 2007 to handle the situation where the JMSGroupSeq property
  had been set to either null or a non-numeric value. These
  changes, which were done under APAR IY95181, caught a
  NumberFormatException that was thrown when the WebSphere MQ
  classes for JMS tried to convert the JMSXGroupSeq property into
  an integer. In this situation, the MsgSeqNumber property of the
  underlying WebSphere MQ message was left unset. The WebSphere
  MQ message still had the MQMF_MSG_IN_GROUP flag set, however.
  
  The code changes for IY95181 were ported into WebSphere MQ
  V7.0.0.0 WebSphere MQ messaging provider migration mode before
  the release of the product. However, no changes were made to
  the WebSphere MQ messaging provider normal mode, which still
  expected the JMSXGroupSeq property to always be set to an
  integer value.
  
  This meant that, if an application was running in WebSphere MQ
  messaging provider normal mode and set the JMSXGroupSeq
  property to a non-numeric value, or null, then the WebSphere MQ
  V7.0.1, V7.1 and V7.5 classes for JMS would throw a
  NumberFormatException when trying to turn the property value
  into an integer.
  

Problem conclusion

• The WebSphere MQ V7.0.1, V7.1 and V7.5 classes for JMS have
  been updated to catch a NumberFormatException when trying to
  convert the JMSXGroupSeq property into an integer value when
  running in WebSphere MQ messaging provider normal mode. In
  this situation, the WebSphere MQ classes for JMS will leave the
  JMSXGroupSeq property unset.
  
  The MQMF_MSG_IN_GROUP flag is still set on the underlying
  WebSphere MQ message, to maintain consistency with the
  WebSphere MQ V6 classes for JMS and the WebSphere MQ messaging
  provider migration mode provided by the WebSphere MQ V7.0.1,
  V7.1 and V7.5 classes for JMS.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
                     v7.0
  Platform           Fix Pack 7.0.1.10
  --------           --------------------
  Windows            U200352
  AIX                U853055
  HP-UX (PA-RISC)    U853082
  HP-UX (Itanium)    U853087
  Solaris (SPARC)    U853083
  Solaris (x86-64)   U853089
  iSeries            7.0.1.10
  Linux (x86)        U853084
  Linux (x86-64)     U853088
  Linux (zSeries)    U853085
  Linux (Power)      U853086
  zOS                7.0.1.10
  
                     v7.1
  Platform           Fix Pack 7.1.0.3
  --------           --------------------
  Windows            7.1.0.3
  AIX                7.1.0.3
  HP-UX (Itanium)    7.1.0.3
  Solaris (SPARC)    7.1.0.3
  Solaris (x86-64)   7.1.0.3
  iSeries            7.1.0.3
  Linux (x86)        7.1.0.3
  Linux (x86-64)     7.1.0.3
  Linux (zSeries)    7.1.0.3
  Linux (Power)      7.1.0.3
  zOS                7.1.0.3
  
  Platform           v7.5
  --------           --------------------
  Multiplatforms     7.5.0.1
  
  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 LIN X86 V7

• Fixed component ID

  5724H7224

Applicable component levels

• R700 PSY

     UP