PH27131: WASANNOTATIONHELPER MAP MEMORY LEAK

APAR status

• Closed as program error.

Error description

• Outofmemory failure encounted due to WASAnnotationHelper Map
  memory leak.
  
  Depending on the requests, certain resources can
  be put into the server WASAnnotationHelper's Map. If those
  resources are not removed from the Map accordingly at the end
  of the each request (assume the resources are at the request
  scoped), they will stay in the Map and increase the memory (i.e
  size of that Map).
  
  WASAnnotationHelper's Map is new with
  Websphere V9.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server versions   *
  *                  9.0 users of JavaServer Faces (JSF)         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Memory leak in WASAnnotationHelper      *
  *                      caused by JSF SessionScoped and         *
  *                      ViewScoped bean replication             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A map in the WebContainer - WASAnnotationHelper - is used to
  keep track of the lifecycle for managed beans. In typical
  scenarios, JSF SessionScoped beans are added to the
  WASAnnotationHelper map when a session begins and then removed
  when that session ends.
  In a high availability environment with
  session persistence, a given session can be serviced by
  multiple servers, and so a session might start on one server
  and end on another. In that case, it is possible for JSF
  beans to leak, since the JSF implementation only cleans up
  managed beans from the WASAnnotationHelper map when it
  receives certain end of session events.
  

Problem conclusion

• The JSF implementation was updated to more aggressively
  destroy the SessionScoped and ViewScoped beans it manages.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.5.6. 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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R900 PSY

     UP