PM51682: SIP REQUESTS CAN BE IMPROPERLY INIATALIZED BY SUPPLYING A PARAMETER WHICH IS LINKED WITH ANOTHER REQUEST/SESSION

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

• When using the method
  
  SipServletRequest createRequest(SipSession session,
  SipServletRequest origRequest, Map<String,List<String>>
  headerMap) throws IllegalArgumentException,
  NullPointerException;
  
  it is possible to provide an origRequest parameter which is
  already linked with another request/session, causing the
  request to persist in memory longer than may be desired, which
  can effectively create a memory leak.
  

Local fix

• supply an origRequest parameter which is newly initialized
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All Session Initiation Protocol (SIP)       *
  *                  container users of IBM WebSphere            *
  *                  Application Server V8.0                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: The SIP container is throwing an        *
  *                      OutOfMemory exception when using        *
  *                      b2buahelper                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The SIP container save references to all linked requests even
  if the application does not have a reference to the request.
  

Problem conclusion

• The SIP container is not holding a reference to all linked
  requests. When the application removes the last reference to
  the request the request object is collected.
  
  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:

  PM49914

• 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