PM46348: SIP CONTAINER DOES NOT CANCEL THE SECOND CONTACT FROM A PARALLEL FORK.

8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• Application recieves an INVITE.  It parallel forks the INVITE to
  2 contacts.
  
  Both contacts send a 180 Ringing at the same time - both 180
  ringings are forwarded back to the caller.
  
  Both contacts then send a 200 OK at the same time.
  
  Websphere Application Server forwards one of the 200 OK's back
  to the caller but does not send a CANCEL to the second contact
  and does not send the 200 OK from the second contact back to the
  caller.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: When application is forking an INVITE   *
  *                      request in parallel mode, and 2 final   *
  *                      responses come back at the same         *
  *                      instance, the 2nd response might not    *
  *                      reach the caller, when application      *
  *                      composition was used                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an application router is used to route internally between 2
  or more proxy applications, and the last application does a
  parallel forking, then in a case of a race condition between the
  2 final responses, the 2nd response (which is received as a
  'stray' without a transaction) that arrives at the last
  application in the chain, will not be sent back in a loopback to
  the previous one, and will not arrive back to the original
  caller.
  

Problem conclusion

• Problem fixed to identify the incoming stray response as such
  that requires a loopback forwarding in a case of composition.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.2.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP