Fixes are available
PK38940; 6.1.0.7: memory leak appears with configuration objects for diagnostic
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
6.1.0.9: WebSphere Application Server V6.1 Fix Pack 9 for Solaris
APAR status
Closed as program error.
Error description
Heap usage increases over time which leads to an OutOfMemory condition. Analysis of a heapdump shows that the following objects are taking up an increasing amount of space: 40,543,128 [304] 47 class com/ibm/wsspi/rasdiag/DiagnosticConfigHome 40,539,056 [56] 2 java/util/Hashtable 0xa8089170 40,539,000 [2,064] 511 array of java/util/Hashtable$Entry 0xaac7ef20 6,300,888 [40] 3 java/util/Hashtable$HashtableCacheHashEntry 196,632 [40] 4 java/util/Hashtable$HashtableCacheHashEntry 196,384 [40] 4 java/util/Hashtable$HashtableCacheHashEntry 196,336 [40] 4 java/util/Hashtable$HashtableCacheHashEntry 196,296 [40] 4 java/util/Hashtable$HashtableCacheHashEntry 196,240 [40] 4 java/util/Hashtable$HashtableCacheHashEntry
Local fix
none, restart the server
Problem summary
**************************************************************** * USERS AFFECTED: Customers using JMS in IBM WebSphere * * Application Server version 6.1 * **************************************************************** * PROBLEM DESCRIPTION: Slow memory leak occurs with JMS * * Transient Connection Pools. The * * DiagnosticConfig hashMap leaks. * **************************************************************** * RECOMMENDATION: * **************************************************************** Transient JMS Connection Pools retrieve a DiagnosticConfig in order to enable the DP interface, but had no means of releasing it when completed.
Problem conclusion
The RasDiag service which handles the DiagnosticConfig objects put in place a mechanism to free the resources, and the J2C component now uses this. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.9. 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 number
PK38940
Reported component name
WEBSPH APP SERV
Reported component ID
5724J0800
Reported release
60I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-02-07
Closed date
2007-03-27
Last modified date
2007-03-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
RAS DIAG
Fix information
Fixed component name
WEBSPH APP SERV
Fixed component ID
5724J0800
Applicable component levels
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
Document Information
Modified date:
29 December 2021