Fixes are available
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
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
In core groups that do not have core group bridges configured, a helper service of the core group bridge stores a small amount of data (typically less than 500 KB) on the core group coordinator in the event a core group bridge is added to the topology. However, this data does not get stored efficiently and results in a small memory leak. Over a period of time, this can lead to an OutOfMemory on the core group coordinator. The magnitude of the problem varies depending on the size of the core group and the enabled services. Typically, this problem is not noticeable in most core groups. . One instance of "com.ibm.ws.cgbridge.core.impl.CGBridgeSubscriptionRouter" loaded occupies 1,036,244,312 (96.51%) bytes. The memory is accumulated in one instance of "java.util.LinkedHashMap". 1,071,287,680 (97%) ?112? 17 com/ibm/ws/hamanager/bboard/LocalBulletinBoardStateManager 0x48b390f8 1,071,186,064 (97%) ?184? 28 com/ibm/ws/hamanager/coordinator/impl/CoordinatorImpl 0x48acd420 1,062,314,880 (96%) ?64? 8 com/ibm/ws/hamanager/coordinator/impl/GlobalBBoardUnifiedStateMa nager 0x48b43f88 1,062,314,144 (96%) ?32? 1 java/util/ArrayList 0x48b440d8 1,062,314,112 (96%) ?32? 1 array of java/lang/Object 0x48b440f8 1,062,314,080 (96%) ?152? 21 com/ibm/ws/cgbridge/core/impl/CGBridgeSubscriptionRouter 0x48e5e910 1,062,292,104 (96%) ?16? 1 java/util/LinkedHashSet 0x48e5e9f8 1,062,292,088 (96%) ?56? 4 java/util/LinkedHashMap 0x48e5ea08 1,045,513,512 (94%) ?40? 4 java/util/LinkedHashMap $LinkedHashMapEntry 0x7fe0dad0 1,045,512,136 (94%) ?40? 5 java/util/LinkedHashMap $LinkedHashMapEntry 0x7fe0da90 1,045,510,936 (94%) ?40? 5 java/util/LinkedHashMap $LinkedHashMapEntry 0x7fe0da50 1,045,510,296 (94%) ?40? 5 java/util/LinkedHashMap $LinkedHashMapEntry 0x7fe0da10 ---> java.util.LinkedHashMap$LinkedHashMapEntry?2097152? @ 0x7062d590 . .------------------------------ One instance of "com.ibm.ws.cgbridge.core.impl.CGBridgeSubscriptionRouter" loaded occupies 1,036,244,312 (96.51%) bytes. The memory is accumulated in one instance of "java.util.LinkedHashMap". 1,071,287,680 (97%) ?112? 17 com/ibm/ws/hamanager/bboard/LocalBulletinBoardStateManager 0x48b390f8 1,071,186,064 (97%) ?184? 28 com/ibm/ws/hamanager/coordinator/impl/CoordinatorImpl 0x48acd420 1,062,314,880 (96%) ?64? 8 com/ibm/ws/hamanager/coordinator/impl/GlobalBBoardUnifiedStateMa nager 0x48b43f88 1,062,314,144 (96%) ?32? 1 java/util/ArrayList 0x48b440d8 1,062,314,112 (96%) ?32? 1 array of java/lang/Object 0x48b440f8 1,062,314,080 (96%) ?152? 21 com/ibm/ws/cgbridge/core/impl/CGBridgeSubscriptionRouter 0x48e5e910 1,062,292,104 (96%) ?16? 1 java/util/LinkedHashSet 0x48e5e9f8 1,062,292,088 (96%) ?56? 4 java/util/LinkedHashMap 0x48e5ea08 . .----------------------------------- SystemOut from problem timeframe shows: . [2/6/11 12:29:16:450 EST] 0000b756 ODCGroup W ODCF0002E: Exception: java.lang.OutOfMemoryError at java.lang.Class.getDeclaredFieldImpl(Native Method) at java.lang.Class.getDeclaredField(Class.java:510) at java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java :1622) at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:64) at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:437)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Network Deployment edition, V6.1 * * and V7.0 * **************************************************************** * PROBLEM DESCRIPTION: The core group bridge service does * * not properly cache subjects and * * causes a small memory leak. * **************************************************************** * RECOMMENDATION: * **************************************************************** Version 7.0 only: In core groups that do not have core group bridges configured, a helper service of the core group bridge stores a small amount of data (typically less than 500 KB) on the core group coordinator in the event a core group bridge is added to the topology. However, this data does not get stored efficiently and results in a small memory leak. Over a period of time, this can lead to an out-of-memory condition on the core group coordinator. The magnitude of the problem varies depending on the size of the core group and the enabled services. Versions 7.0 and 6.1: If a core group has a core group bridge configured and the core group bridge is not used, then the helper service of the core group bridge will store data in this case also. Over a period of time, this can also lead to an out-of-memory condition on the core group coordinator. NOTE: Both of these scenarios are not problematic in typical core group configurations due to the small amount of data being stored.
Problem conclusion
The core group bridge service was modified to efficiently store bulletin board subjects and prevent any related memory leaks. The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.33 and 7.0.0.11. 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
PM10894
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
60I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-03-25
Closed date
2010-04-07
Last modified date
2011-11-09
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
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:
24 October 2021