PM54852: SIP - SESSIONREADYTOINVALIDATE() IS NOT BEING CALLED WHEN MULTIPLE APPLICATIONS ARE DEPLOYED.

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

• sessionReadyToInvalidate() is not being called when multiple
  applications are deployed.  When only one application is
  deployed, the call to the method occurs as expected.
  Session Initiation Protocol (SIP) container.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: Transaction User (TU) does not get      *
  *                      cleaned up from memory when session     *
  *                      terminates, and invalidateWhenReady is  *
  *                      enabled.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  On a proxy application scenario, when a dialog terminating
  subsequent request comes from the side of the initial request
  recipient, the TU might not get searched with the correct dialog
  key, and might not be found, and so will not get cleaned up when
  session terminates.
  

Problem conclusion

• TU key lookup in that proxy scenario was fixed.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.3.  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:

  PM53078

• 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