PM54350: SIP CONTAINER CREATES EXTRA SIPAPPLICATIONSESSIONS WHICH ARE NEVER INVALIDATED

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

• General scenario: customer handles a subscribe from an
  endpoint.  We back-to-back this, send a polling subscribe, and
  then  send a notify to the subscriber.
  The SipApplicationSessions container is creating 2
  extra SASs for some reason  these don't appear to go away.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: A new ApplicationSession would be       *
  *                      created from an invalid Session         *
  *                      Initiation Protocol (SIP) session       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A new SipApplicationSession would be created from a call to
  getApplicationSession() on a SIP session that was already
  invalidated.
  

Problem conclusion

• Now a call to getApplicationSession() will never create a new
  SipApplicationSession, but will return any existing one, or
  null.
  
  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:

• 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