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

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 IBM WebSphere Application Server        *
  *                  Feature                                     *
  *                  Pack for Communications Enabled             *
  *                  Applications                                *
  *                  (CEA) users                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: Transaction User (TU) does not get      *
  *                      cleaned up from memory when session     *
  *                      terminates.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1. When sessions are not created explicitly by the application,
  the related Transaction User (TU) would not get cleaned up from
  memory with the invalidateWhenReady mechanism
  2. On certain proxy scenarios, TU would not get cleaned up.
  

Problem conclusion

• Set SIP container custom property:
  "enable.ready.to.invalidate.without.session"
  to "true"
  to have readyToInvalidate mechanism clear up TUs without a
  session explicitly created.
  
  Set SIP container custom property:
  "create.sessions.when.listeners.exist";
  to "true"
  
  So that sessions will get created by the container whenever a
  session listener was defined, so it will get called with that
  session passed to it.
  
  Issue with proxy scenario not cleaning up problem fixed.
  
  The fix for this APAR is currently targeted for inclusion in
  fix
  pack 1.0.0.13. 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:

  PM54852

Fix information

• Fixed component name

  CEA FEATUREPACK

• Fixed component ID

  5724J0855

Applicable component levels

• R700 PSY

     UP