PM39905: SIP ASYNCHRONOUS API IS CREATING NEW SIPAPPLICATIONSESSION OBJECT FOR EVERY TASK, IT IS NEVER EXPLICITLY INVALIDATED

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

• Session Initiation Protocol (SIP) asynchronous API created new
  SipApplicationSession object for every task. Because it is
  never explicitly invalidated, if the default
  SipApplicationSession expiration is set by the application to
  "never" it will never expire and the SIP container will leak
  memory.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: Session Initiation Protocol (SIP)       *
  *                      asynchronous API creates a new          *
  *                      SipApplicationSession object for        *
  *                      every task                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  SIP asynchronous api creates a new SipApplicationSession object
  for every task. Because it is never explicitly invalidated if
  the default SipApplicationSession expiration is set by the
  application to "never" it will never expire and the SIP
  container will leak memory.
  

Problem conclusion

• One SipApplicationSession is now used for all SIP asynchronous
  tasks.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.1.  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:

  PM36471

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R800 PSY

     UP