IT19573: MQ-JMS: CANNOT GET OR BROWSE JMS MESSAGE PROPERTY WHICH CONTAINSTHE STRING VALUE " XSI:NIL".

APAR status

• Closed as program error.

Error description

• The WebSphere MQ classes for JMS cannot parse a message that has
  been browsed or got from a queue if the message contains an
  MQRFH2 header with a <usr> folder containing a custom user
  String property with a value that contains the string "
  xsi:nil".
  
  For example:
  
    <usr>
      <MyProperty> xsi:nil</MyProperty>
    </usr>
  
  When a message containing a <usr> folder in the MQRFH2 header
  similar to the above is consumed by the MQ classes for JMS, it
  will actually result in a message property with key:
  
    MyProperty>
  
  and value:
  
    null
  
  being set on the JMS Message object returned to the application.
   Therefore, calling:
  
    getStringProperty("MyProperty")
  
  on the JMS Message object will result in a null object being
  returned.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of the:
  
    - WebSphere MQ V7.5.0.6 and later classes for JMS
    - IBM MQ V8.0.0.4 and later classes for JMS
    - IBM MQ V9.0.0.0 and later classes for JMS
  
  who consume messages that contain an MQRFH2 header with a <usr>
  folder that contains a String message property with a value that
  includes the string " xsi:nil".
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When using a version of the MQ classes for JMS that includes the
  fix for APAR IT08928:
  
    http://www-01.ibm.com/support/docview.wss?uid=swg1IT08928
  
  message properties with a value that contains the String "
  xsi:nil" could not be parsed correctly.  This was because part
  of the parsing logic for the <usr> folder of the MQRFH2 header
  was looking for the string value " xsi:nil" in an attempt to
  identify null elements (properties that do not have values).
  For example, the following <usr> folder has three properties,
  named myElement1, myElement2 and myElement3.  The first two both
  have null values but are represented in subtlety different
  forms. The third property, myElement3, does contain a value
  where part of the property value contains the String " xsi:nil":
  
    <usr>
      <myElement1 xsi:nil='true'/>
      <myElement2 xsi:nil="true"></myElement2>
      <myElement3>XML nillible element attribute
  xsi:nil="true"</myElement3>
    <usr>
  
  The parsing logic did not differentiate between the string "
  xsi:nil" being found as an attribute within a named element (as
  it is with myElement1 and myElement2 above) and it being
  contained within the value of a named element (as it is with
  myElement3).
  

Problem conclusion

• The MQ classes for JMS have been update such that message
  property values containing the string " xsi:nil" are now parsed
  correctly.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.5       7.5.0.8
  v8.0       8.0.0.7
  v9.0 LTS   9.0.0.2
  
  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 BASE MULTIP

• Fixed component ID

  5724H7251

Applicable component levels

• R800 PSY

     UP