IC68264: NULLPOINTEREXCEPTION OCCURS WHILE PROCESSING FAILED EVENTS

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

• While processing a failed event, a NullPointerException may be
  thrown due to the fact that no contextual SCA Module is present.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of WebSphere Enterprise Service Bus    *
  *                 and WebSphere Process Server v6.2 and v7     *
  *                 who use LTPA security tokens with JMS        *
  *                 Bindings.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: When a callback message expires an      *
  *                      exception is thrown by the flow. If     *
  *                      the callback message cannot be          *
  *                      processed by the SCA layer, such as     *
  *                      if the LTPA tokens have expired,        *
  *                      a Failed Event is generated. The        *
  *                      Failed Event generated cannot be        *
  *                      handled by the Failed Event manager.    *
  ****************************************************************
  * RECOMMENDATION: If you use JMS bindings and have Failed      *
  *                 Events generated when callback messages      *
  *                 expire you are advised to install the fix    *
  *                 pack which contains the code update          *
  *                 associated with this APAR.                   *
  ****************************************************************
  A ServiceExpirationRuntimeException is thrown when a callback
  message expires. Ordinarily this does not result in a Failed
  Event being generated. However, if the SCA layer is unable to
  process the notification before the Async hop, such as if the
  LTPA tokens have expired, then a Failed Event is generated.
  The FE being generated cannot be processed by the Failed Event
  Manager due to the way the body is stored. This fix changes
  the way the body is stored, thus allowing the Failed Event to
  be handled by the FEM.
  

Problem conclusion

• The code was modified such that the Failed Event generated was
  changed to allow the Failed Event Manager to process it.
  
  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:
       6.2.0 Fix Pack 4 (v6.2.0.4)
       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 PSY

     UP

• R700 PSY

     UP