PI20171: EJBCONFIGDATA OBJECT REFERENCE NOT REMOVED WHEN DONE, CAUSING MEMORY LEAK AND HIGH MEMORY CONSUMPTION

8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• The EJBConfigData holds a reference to the DD objects.
  EJBContainer has dropped its reference to this object, but the
  security object still holds a reference.  EJBContainer cannot
  clear the references in the EJBConfigData, as security actually
  uses them, and EJBContainer cannot determine when security is
  done.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server who run Enterprice Java Beans (EJB)  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Memory usage can be improved when       *
  *                      running EJBs when application security  *
  *                      is enabled.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Security code keeps reference to EJB data.
  As the EJB specification evolves, the size of EJB data that is
  necessary to support the specification is increased.
  As a result, increased memory area is taken up by security
  code if a large number of EJBs are running on the system.
  

Problem conclusion

• Following top-level security custom property has been
  introduced with this apar.
  
  Custom property:
  com.ibm.websphere.security.release.ejb.reference
  Value:
  true (release ejb data that is not related to security)
  Default is false.
  
  When the value is set to true, security code will only keep
  reference to security-related EJB data for better memory usage.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.5.  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

• R850 PSY

     UP