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
After an upgrade to fixpack 8.5.5.3 or above, memory growth seen leading to an OutOfMemmory error or slow performance due to excessive time spent in garbage collection. This could also appear to be a hang. Analysis of a heap dump shows a large number of com/ibm/ejs/j2c/J2CGlobalConfigProperties objects in the heap. This occurs when the "_" character is used in a JMS connection factory name. During the cleanup of the connection pool associated with a JMSManagedConnection, an equality check fails resulting in skipping the de-registration. Basically the comparison of cfDetailsKey and cfKey are not matching. The J2CGlobalConfigProperties objects are not getting de-registered from the diagnostic AlertConfig.
Local fix
Remove the "_" character from the JMS connection factory JNDI name
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.5 * **************************************************************** * PROBLEM DESCRIPTION: JMS Connection factory not destroyed * * when their name contain "_" character * * and can lead to memory leak. * **************************************************************** * RECOMMENDATION: * **************************************************************** Apar PI09343 added the delimiter "_" in the connection factory long key used internally in the J2C code for parsing and extracting the connection factory key from a long key. So if the connection factory jndi name defined contains a underscore "_" already, then it affected the parsing which prevents the cleanup of the connection factory that can lead to memory leaks. This APAR addresses this issue by using appropriate delimeter in the J2C code to handle the parsing and cleanup of the J2C connection factories.
Problem conclusion
The WebSphere J2C code has been corrected to handle the parsing issue and ensures the connection factory is properly cleaned up. APAR PI36870 is currently targeted for inclusion in Fix Pack 8.5.5.7 of WebSphere Application Server. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PI36870
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-03-13
Closed date
2015-06-08
Last modified date
2015-06-08
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
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022