IC67969: MQ HEADER EXCEPTIONS THROWN WHEN ATTEMPTING TO REPLAY OR VIEW A FAILED EVENT

WebSphere Enterprise Service Bus V7.0.0 Fix Pack 3 (7.0.0.3)
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 a Failed event is generated on an
  Import binding, if for example a correlation ID cannot be
  found, then on reply users can see exceptions
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Websphere Enterprise Service Bus    *
  *                 and Websphere Process Server v7.0 who are    *
  *                 using MQ Bindings and are using the          *
  *                 Failed Event Manager to attempt to replay    *
  *                 or view a failed event.                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using MQ bindings and a Failed     *
  *                      Event is generated on an Import         *
  *                      binding if for example a correlation    *
  *                      ID cannot be found, then on replay      *
  *                      users  can see Exceptions like the      *
  *                      following:                              *
  *                                                              *
  *                      [4/14/10 14:40:45:366 EDT] 00000092     *
  *                      MQ CWSCA4100E: An MQMD property could   *
  *                      not be accessed. JNDI destinations      *
  *                      used by the WebSphere MQ binding must   *
  *                      have custom properties MDWRITE and      *
  *                      MDREAD set to "YES" and custom          *
  *                      property  MSGBODY set to "MQ".          *
  *                      [4/14/10 14:40:45:366  EDT]             *
  *                      00000092 RemoteExcepti E   CNTR0020E:   *
  *                      EJB threw an unexpected                 *
  *                      (non-declared)                          *
  *                      exception during invocation of method   *
  *                      "getEventDetailForMQ" on bean "BeanId   *
  *                      (wpsFEMgr_7.0.0#wpsFEMgrEJB.jar#        *
  *                      FailedEventManagerEJB, null)".          *
  *                      Exception                               *
  *                      data:                                   *
  *                      java.lang.NumberFormatException:        *
  *                      null at java.lang.Integer.parseInt      *
  *                      (Integer.java:429) at                   *
  *                      java.lang.Integer.                      *
  *                      valueOf(Integer.java:566)               *
  *                                                              *
  *                      These Exceptions occur as the           *
  *                      MQHeaders are not included in the       *
  *                      message that is sent to and replayed    *
  *                      from the FEM.                           *
  *                      The headers are excluded if an          *
  *                      Exception to generate the failed        *
  *                      event occurs before the message has     *
  *                      reached the databinding.                *
  ****************************************************************
  * RECOMMENDATION: If you experience these issues you are       *
  *                 advised to install the fix pack which        *
  *                 contains the code update associated with     *
  *                 this APAR.                                   *
  ****************************************************************
  In Websphere Integration Developer 7, users can generate an MQ
  import binding and configure it to manage recovery for failed
  messages. However, exceptions can occur when the MQHeaders are
  not included in the message that is sent to and replayed from
  the FEM.  The headers are excluded if an Exception to generate
  the  failed event occurs before the message has reached the
  databinding.
  

Problem conclusion

• The code was modified such that the MQ headers are retrieved
  correctly
  
  There are no known side effects associated with this fix.
  There is no known alternative workaround should you encounter
  this problem.
  
  This code fix was targeted to be included in the following fix
  packs:
       7.0.0 Fix Pack 3 (v7.0.0.3)
  

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