PM36669: WEBSPHERE SENDS "481 CALL/TRANSACTION DOES NOT EXIST" TO THE NOTIFY INSTEAD OF TO THE ACTIVE SESS IN THE APP

8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
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

• WebSphere Application Server sends "481 Call/Transaction
  Does Not Exist" to the NOTIFY instead  of passing it to the
  active session in the application server.
  
  "It's a race condition between the 200OK and the NOTIFY coming
  into the container as a response to the SUBSCRIBE. Both messages
  are expected to update the session key with a new remote (To)
  tag, at the point of the race they are handled on two different
  threads, one is removing the entry before it is updated and the
  other (the NOTIFY) is looking for the entry at that moment and
  can't find it (so it returns 481).
  
  WebSphere Application Server V7.0
  Dstributed operating systems.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application Server
  ****************************************************************
  * PROBLEM DESCRIPTION: App Server sends "481 Call/Transaction  *
  *                      Does Not Exist" to the NOTIFY           *
  *                      instead  of the active                  *
  *                      session in the app server.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A race condition between the NOTIFY from a UAS to the 2xx final
  response of a SUBSCRIBE for updating the session identifier,
  caused the NOTIFY to find the session.
  

Problem conclusion

• Race condition resolved
  The fix for this APAR is currently targeted for inclusion in
  fix pack 1.0.0.11.  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:

  PM42176

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R700 PSY

     UP