Fixes are available
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
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.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
APAR status
Closed as program error.
Error description
Customer system runs into OOM conditions. Analysis of the heap shows this stack: ,018,705,728 (70.9%) [16] 1 com/ibm/ws/wim/adapter/ldap/CachedNamingEnumeration 0x5858fe58 2,018,705,712 (70.9%) [24] 1 java/util/Vector 0x58590cd0 2,018,705,688 (70.9%) [4,194,320] 975,316 array of java/lang/Object 0x88993ea8 3,264 (0%) [32] 3 javax/naming/directory/SearchResult 0x57685330 2,504 (0%) [32] 3 javax/naming/directory/SearchResult 0x92b47e18 2,504 (0%) [32] 3 javax/naming/directory/SearchResult 0x7fedf310 2,504 (0%) [32] 3 javax/naming/directory/SearchResult 0x8c58f530 2,504 (0%) [32] 3 javax/naming/directory/SearchResult 0x84a3cad0 2,496 (0%) [32] 3 javax/naming/directory/SearchResult 0x531146d8 2,496 (0%) [32] 3 javax/naming/directory/SearchResult 0x5c9c5958 There are 975,305 more children
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: Getting Out Of memory exception when * * there are a large number * * (approximately 10000) of users in the * * LDAP repsoitory. * **************************************************************** * RECOMMENDATION: * **************************************************************** When an LDAP repository contains a large number (approximately 10000) of users, an OutOfMemory occurs due to javax.naming.directory.searchResult objects.
Problem conclusion
This fix corrects the code to limit creating searchResults objects to the maxSearchResults parameter value mentioned in wimconfig.xml. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.7 and 8.5.5.1. 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
PM82122
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-02-05
Closed date
2013-04-23
Last modified date
2013-10-04
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
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
11 January 2022