PM75846: NoSuchElementException thrown when JMS subscriber uses a greater-than symbol in the message selector.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The user is running a WebSphere MQ V6 JMS application, or a V7
  JMS application using PROVIDERVERSION=6. The application is
  using BROKERVERSION 2 (MQJMS_BROKER_V2).
  
  When a JMS TopicSubscriber attempts to open a durable
  subscription specifying a message selector which contains a
  greater-than symbol the following error is thrown:
  
  java.util.NoSuchElementException
  at
  java.util.StringTokenizer.nextToken(StringTokenizer.java:332)
  at
  com.ibm.msg.client.wmq.v6.jms.internal.RFH2BrokerMessageImpl.
  parsePubSubFolder(RFH2BrokerMessageImpl.java:635)
  ....
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
  *                 Release 0 Modification 1 and WebSphere MQ    *
  *                 for z/OS Version 7 Release 1 Modification 0. *
  ****************************************************************
  * PROBLEM DESCRIPTION: Response messages for queued publish/   *
  *                      subscribe can contain non-escaped XML   *
  *                      control characters in RFH2 string       *
  *                      fields which may cause compatibility    *
  *                      issues with existing publish/subscribe  *
  *                      applications.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Queued publish/subscribe applications may receive reply messages
  containing XML control characters that aren't escaped, within
  string fields in the RFH2 header. These characters include
  greater-than (>), double quote (") and apostrophe (').These
  non-escaped strings may cause compatibility with existing
  publish/subscribe applications.
  
  Compatibility issues noted due to this include:
  
  Websphere MQ V7 JMS applications and Websphere MQ V6 JMS
  applications using PROVIDERVERSION=6 receiving a
  java.util.NoSuchElementException exception when a JMS
  TopicSubscriber attempts to open a durable subscription with
  a message selector specified, which contains XML control
  characters.
  

Problem conclusion

• The code has been amended to escape all XML control characters
  that appear in RFH2 string fields that are used in queued
  publish/subscribe messages.
  010Y
  100Y
  CMQXFAIR
  

Temporary fix

Comments

APAR Information

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

  IV27891

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

  UK92610 UK92611

Modules/Macros

•    CMQXFAIR
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R010 PSY UK92610

     UP13/04/04 P F304

• R100 PSY UK92611

     UP13/04/04 P F304

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.