IC80371: RESPONSE (FAULT) FLOW IS NOT INVOKED WHEN USING ASYNCWITHCALLBACK

WebSphere Process Server V7.0.0 Fix Pack 5 (V7.0.0.5)
WebSphere Enterprise Service Bus V7.0.0 Fix Pack 5 (7.0.0.5)
WebSphere Enterprise Service Bus V7.5.1 Fix Pack 1 (7.5.1.1)
Version 7.5.1 Fix Pack 1 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• A BPM process has an MQ binding connecting to MQ on zOS. The
  process server is running and tested to ensure is working. MQ is
  stopped. When try again there is a failure connecting to MQ as
  expected.
  
  Once MQ is restarted the process remains in state running. The
  activation spec assoicated is stil in a state of active. The
  process never moves on.
  
   The issue is that the ServiceRuntimeException response is
  returned immediately in the SCA message used to invoke the
  asyncWithCallback - rather than as an async Callback.
  The exception is identified as an unmodelled fault, and retry
  function in WESB would correctly retry the failed invocation.
  When retries are all used up (in this particular case there are
  no retries configured) an exception SMO is returned to the
  Callout.  However, for asyncWithCallback invocation style, the
  response (fault) flow is not invoked  - it is only invoked by
  Callbacks.
  .
     The following are logged
  [08/12/11 17:00:17:936 GMT] 000000b3 SibMessage    W   ?:?
  CWSJY0003W: JMSCC3036: An exception has been delivered to the
  connections exception listener: '
    Message : javax.jms.JMSException: MQJMS1107: A
  problem with the connection has occurred.
    Class : class javax.jms.JMSException
  .
  .
  [08/12/11 17:00:18:293 GMT] 000000b3 SibMessage    W   ?:?
  CWSJY0003W:
  MQJCA4003: A recoverable exception occurred in the JMS layer:
  'MQJMS2003: failed to disconnect queue manager.'
  

Local fix

Problem summary

• The issue is that the SRE exception response is returned
  immediately in the SCA message used to invoke the
  asyncWithCallback - rather than as an async Callback. The
  exception is identified as an unmodelled fault, and retry
  function in WESB would correctly retry the failed invocation.
  When retries are all used up an exception SMO is returned to the
  Callout. However, for asyncWithCallback invocation style, the
  response (fault) flow is not invoked  - it is only invoked by
  Callbacks.
  

Problem conclusion

• The code was modified to ensure that the flow is invoked
  correctly.
  
  This code fix was targeted to be included in the following fix
  packs:
  
  7.0.0 Fix Pack 5 (v7.0.0.5)
  7.5.1 Fix Pack 1 (v7.5.1.1)
  

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

• R700 PSY

     UP

• R750 PSY

     UP

• R751 PSY

     UP

• R100 PSN

     UP

• R200 PSN

     UP

• R300 PSN

     UP

• R612 PSN

     UP

• R620 PSN

     UP