Fixes are available
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
An appserver might hang intermittently during startup. The hung thread will show a stack trace similar to that below: ThreadMonitor W WSVR0605W: Thread "server.startup : 0" (000000b8) has been active for 676877 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung. at java.util.HashMap.rehash(HashMap.java:790) at java.util.HashMap.rehash(HashMap.java:827) at java.util.HashMap.putImpl(HashMap.java:711) at java.util.HashMap.put(HashMap.java:689) at com.ibm.ws.naming.java.JavaNameSpaceManagerImpl. getJavaModuleNameSpace(JavaNameSpaceManagerImpl.java:195) at com.ibm.ws.naming.java.JavaNameSpaceManagerImpl. ...
Local fix
No work around at this time.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server using JEE6 java:global, java:module, * * java:app naming APIS. * **************************************************************** * PROBLEM DESCRIPTION: Intermittent Appserver hang during * * startup * **************************************************************** * RECOMMENDATION: Install a fixpack containing this APAR. * **************************************************************** A synchronization problem could cause hashmap operations to hang when certain JEE6 naming operations are being performed.
Problem conclusion
Synchronization is changed so the problem no longer occurs. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.8 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
PM88810
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-05-10
Closed date
2013-07-17
Last modified date
2013-07-17
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