IC70603: MQ HEADERS NOT PROCESSED CORRECTLY WHEN HEADER FIELDS CONTAIN NULL CHARACTERS

WebSphere Enterprise Service Bus V7.0.0 Fix Pack 4 (7.0.0.4)

APAR status

• Closed as program error.

Error description

• When using MQ bindings and header information passed to the
  binding contains null characters the BOXML Serializer fails to
  serialize the BO created by the binding. Users will see the
  folling error for example:
  
  [6/21/10 11:02:42:990 EDT]     FFDC
  Exception:java.lang.RuntimeException
  SourceId:java.lang.RuntimeException caught trying to serialize
  BO
  HeadersTypeImpl: HeadersType@254a254a
  (SMOHeader=SMOHeaderType@25552555,
  MQHeader=MQHeaderType@1c291c29)
  ProbeId:214
  java.lang.RuntimeException: An invalid XML character (Unicode:
  0x0)
  was found in the element content:
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users may experience this issue when using   *
  *                 MQ bindings. If the header information       *
  *                 contains null characters, the business       *
  *                 object will not be serialized. This issue    *
  *                 affects users of Websphere Enterprise        *
  *                 Service Bus and WebSphere Process Server v7  *
  ****************************************************************
  * PROBLEM DESCRIPTION: MQ headers are not processed            *
  *                      correctly when header fields contain    *
  *                      NULL characters.                        *
  ****************************************************************
  * RECOMMENDATION: If you encounter this problem, you are       *
  *                 advised to install the code fix which is     *
  *                 associated with this APAR.                   *
  ****************************************************************
  The BOXML Serializer fails to serialize the BO created by the
  binding, if supplied with a header containing NULL characters.
  

Problem conclusion

• The product code was modified to correct this issue.
  
  The fix was targeted to be included in the following fix packs:
  
       v7.0.0 Fix Pack 4 (7.0.0.4)
  

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

  WEB ESB FOR WIN

• Fixed component ID

  5724I8200

Applicable component levels

• R100 PSN

     UP

• R200 PSN

     UP

• R300 PSN

     UP

• R612 PSN

     UP

• R620 PSN

     UP

• R700 PSY

     UP