Fixes are available
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.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
There is a resource leak in the CosNaming service which can use all available memory. Examination of a server heapdump will reveal a large number (many thousands) of live objects of type org.apache.yoko.orb.CosNaming.tnaming2.NamingContextImpl$POA Servant$ReadOnly.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile - JNDI * **************************************************************** * PROBLEM DESCRIPTION: Server with IIOP clients fills heap and * * throws OutOfMemoryError. * **************************************************************** * RECOMMENDATION: * **************************************************************** There is a resource leak in the CosNaming service which can use all available memory. Examination of a server heapdump will reveal a large number (many thousands) of live objects of type org.apache.yoko.orb.CosNaming.tnaming2.NamingContextImpl$POAServ ant$ReadOnly.
Problem conclusion
The POA servant objects for the CosNaming service naming contexts are now created and activated with unique IDs. If a servant already exists for a given ID, it is re-used. Multiple invocations of the CosNaming service should no longer result in heap exhaustion. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.7. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
There is no way to work around this issue other than to restart the server repeatedly, which has significant drawbacks.
Comments
APAR Information
APAR number
PI46803
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-08-12
Closed date
2015-08-13
Last modified date
2015-08-13
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
WAS LIBERTY COR
Fixed component ID
5725L2900
Applicable component levels
R855 PSY
UP
Document Information
Modified date:
28 April 2022