Fixes are available
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
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: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
The following data will be written to a heapdump One instance of "com.ibm.ws.cgbridge.core.impl.WorkDispatcher" loaded by "org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader @ 0x7000000071d6848" occupies 501,740,968 (88.61%) bytes Shortest Paths To the Accumulation Point com.ibm.ws.cgbridge.core.impl.WorkDispatcher @ 0x700000003c82160 96 com.ibm.ws.cgbridge.core.impl.CGBridgeService @ 0x70000000996fdf0 com.ibm.ws.cluster.propagation.bulletinboard.BBDescriptionManage r @ org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader @ com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializ com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitiali Accumulated Objects com.ibm.ws.cgbridge.core.impl.WorkDispatcher @ 0x700000003c82160 96 java.util.HashMap @ 0x700000003c822b0 80 501,729,416 88.61% java.util.HashMap @ 0x700000003c82300 80 11,216 0.00% java.util.LinkedList @ 0x700000003c821f0 48 96 0.00% java.util.LinkedList @ 0x700000003c82250 48 96 0.00% java.lang.Object @ 0x700000003c821c0 24 24 0.00% java.lang.Object @ 0x700000003c821d8 24 24 0.00%
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All core group bridge users of IBM * * WebSphere Application Server V6.1 and V7.0 * **************************************************************** * PROBLEM DESCRIPTION: Memory leak results from repeatedly * * restarting core group bridge servers. * **************************************************************** * RECOMMENDATION: * **************************************************************** The memory leak only occurs whenever a bridge in the local core group is stopped or started. The memory leak grows when bridges are stopped and restarted, but does not occur during normal operation. You may be able to wait until your normal maintenance window if your network is stable. Refer to the following example scenarios for more details about when the memory leak occurs. Example Topology CoreGroup1 cg1Bridge1 (bridge & coordinator) cg1Bridge2 (bridge) clusterMember1 CoreGroup2 cg2Bridge1 (bridge & coordinator) cg2Bridge2 (bridge) clusterMember2 Scenario1 cg2Bridge1 is stopped and restarted - no memory leak occurs on cg1Bridge1 and cg1Bridge2, but cg2Bridge2 has memory leak. Scenario2 clusterMember1 is stopped and restarted - no memory leak occurs. Scenario3 cg1Bridge2 is stopped and restarted - cg1Bridge1 has memory leak, but cg2Bridge1 and cg2Bridge2 do not have memory leak. Customers that do not restart their bridges and customers who restart all of their core group bridges likely will not be affected by this problem. However, customers with network connectivity issues between bridges may be affected because network interruptions are the functional equivalent of restarting bridges.
Problem conclusion
A code change was made to resolve the memory leak. The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.37 and 7.0.0.17. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Provided fix to customer
Comments
APAR Information
APAR number
PM27262
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-11-23
Closed date
2011-02-03
Last modified date
2011-02-03
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 APP S
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
R700 PSY
UP
Document Information
Modified date:
27 October 2021