IC59660: 'FAN OUT/FAN IN' FLOWS NOT STOPPING WHEN USING MULTIPLE FLOWS.

WebSphere Process Server V6.2.0 Fix Pack 1 (V6.2.0.1)
WebSphere Enterprise Service Bus V6.2.0 Fix Pack 1 (6.2.0.1)
WebSphere Enterprise Service Bus V6.2.0 Fix Pack 2 (6.2.0.2)

APAR status

• Closed as program error.

Error description

• Problem Description:
  
  A Fan Out primitive can have multiple flows from it that
  eventually lead to a corresponding Fan In primitive. If the
  'stop' terminal of this Fan In primitive is triggered it will
  fire it's 'incomplete' terminal.  This should stop the 'Fan
  Out/Fan In' flows, but any of the multiple flows that have not
  yet been executed will process at this point and will result in
  the following exception, as messages in the other flows are
  processed after the Fan In primitive has stopped:
  
  FlowActionPolicyException: CWSXM0100E: Multiple replies have
  been produced for a single request flow in module
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of WebSphere Enterprise Service Bus    *
  *                 and WebSphere Process Server v6.1.2 or       *
  *                 v6.2 who wish to use Fan In/Fan Out          *
  *                 primitives with multiple paths.              *
  ****************************************************************
  * PROBLEM DESCRIPTION: A Fan Out primitive does not check      *
  *                      that it's corresponding Fan In          *
  *                      primitive is able to accept messages    *
  *                      before firing messages through          *
  *                      remaining paths through the             *
  *                      mediation.                              *
  ****************************************************************
  * RECOMMENDATION: If you use Fan In/Fan Out combinations       *
  *                 with multiple paths and require processing   *
  *                 of any remaining paths to stop after the     *
  *                 Fan In primitive has had it's 'stop'         *
  *                 terminal triggered, you are advised to       *
  *                 install the fix pack which contains the      *
  *                 code update associated with this APAR.       *
  ****************************************************************
  The Fan Out primitive does not check the state of it's
  corresponding Fan In primitive before firing a message through
  any remianing paths. If the Fan In primitive has had it's
  ''stop' terminal triggered, it will not be expecting to receive
  any further messages.
  As the Fan Out primitive does not check
  this, it will continue to send these messages, and when they
  arrive at the Fan In, the observed exception is seen.
  

Problem conclusion

• The code was modified such that the Fan Out primitive is now
  able to check the state of it's corresponding Fan In primitive.
  
  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.1.2 Fix Pack 3 (v6.1.2.3)
       6.2.0 Fix Pack 1 (v6.2.0.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

• R100 PSN

     UP

• R200 PSN

     UP

• R300 PSN

     UP

• R612 PSY

     UP

• R620 PSY

     UP