Fixes are available
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
stopserver script intermittently fails to send signal to Websphere server to stop. The JVM hangs due to waiting on class initialization lock Stack 1: 3XMTHREADBLOCK Waiting on: java/lang/J9VMInternals$ClassInitializationLock@0x00000000802AE8 70 Owned by: <unowned> 3XMHEAPALLOC Heap bytes allocated since last GC cycle=0 (0x0) 3XMTHREADINFO3 Java callstack: 4XESTACKTRACE at com/ibm/ws/logging/WsLoggerFactoryImpl.createWsLogger(WsLoggerFa ctoryImp l.java:79) ... 4XESTACKTRACE at com/ibm/ws/bootstrap/WSLauncher.main(WSLauncher.java:280) Stack 2: 3XMTHREADBLOCK Waiting on: java/lang/J9VMInternals$ClassInitializationLock@0x0000000080152F 10 Owned by: <unowned> 3XMHEAPALLOC Heap bytes allocated since last GC cycle=140312 (0x22418) 3XMTHREADINFO3 Java callstack: 4XESTACKTRACE at com/ibm/ws/logging/WsLoggerConfigurator.configureLogger(WsLogger Configur ator.java:459) 4XESTACKTRACE at com/ibm/ws/logging/WsLoggerFactoryImpl.createWsLogger(WsLoggerFa ctoryImp
Local fix
Use ENDJOB to end the Websphere server.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: Run stopServer script intermittently * * results in hang, fails to stop server. * **************************************************************** * RECOMMENDATION: * **************************************************************** Deadlock may happen if any java class invoke JUL logging eariler than WebSphere application server logging framework initialization, no matter in start or stop process.
Problem conclusion
The problem was caused by different threads access the WsLogger class at the same time when the class is not initialized completely yet. The problem has been corrected. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.15, 8.5.5.14, and 9.0.0.8. 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
PI92935
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-01-25
Closed date
2018-04-15
Last modified date
2018-04-15
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
R900 PSY
UP
Document Information
Modified date:
04 May 2022