Fixes are available
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
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
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
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
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
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
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
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
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 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
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
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
The likeminds thread first acquires a lock on the object com.ibm.ws.bootstrap.WsLogManager, it then attempts to acquire a lock on object java.util.logging.LogManager$LoggerContext but it is blocked by the server startup thread. Meanwhile the server.startup thread acquires a lock on object java.util.logging.LogManager$LoggerContext and is attempting to acquire a lock on object com.ibm.ws.bootstrap.WsLogManager and is blocked as the likeminds thread already has it. It is a race condition with both threads attempting to acquire the same two objects. On the pznLikemindsWorkManager server there will be entries: "java.lang.ThreadGroup[name=pznLikemindsWorkManager: PZN_Utilities,maxpri=10]" daemon prio=3 tid=0x028f6c00 nid=0xbf waiting for monitor entry [0x3a9fd000] java.lang.Thread.State: BLOCKED (on object monitor) at java.util.logging.LogManager$LoggerContext.addLocalLogger(LogMan ager.java:482) - waiting to lock <0x5bc8fcf0> (a java.util.logging.LogManager$LoggerContext) at java.util.logging.LogManager.addLogger(LogManager.java:826) at com.ibm.ws.bootstrap.WsLogManager.getLogger(WsLogManager.java:22 0) - locked <0x5bc847d0> (a com.ibm.ws.bootstrap.WsLogManager) at com.ibm.websphere.personalization.log.LogFactory.getLog(LogFacto ry.java:68) In the server startup log: "server.startup : 1" daemon prio=3 tid=0x0152a800 nid=0x95 waiting for monitor entry [0x3d17e000] java.lang.Thread.State: BLOCKED (on object monitor) at java.util.logging.LogManager.drainLoggerRefQueueBounded(LogManag er.java:787) - waiting to lock <0x5bc847d0> (a com.ibm.ws.bootstrap.WsLogManager) at java.util.logging.LogManager$LoggerContext.addLocalLogger(LogMan ager.java:488) - locked <0x5bc8fcf0> (a java.util.logging.LogManager$LoggerContext) at java.util.logging.LogManager.addLogger(LogManager.java:826) at java.util.logging.LogManager.demandSystemLogger(LogManager.java: 417) at java.util.logging.Logger.demandLogger(Logger.java:287) at java.util.logging.Logger.getLogger(Logger.java:321) - locked <0xcbf8e3d8> (a java.lang.Class for java.util.logging.Logger) at com.sun.jmx.trace.TraceManager.getLogger(TraceManager.java:184) at com.sun.jmx.trace.TraceManager.isSelected(TraceManager.java:197) at com.sun.jmx.trace.Trace.isSelected(Trace.java:89)
Local fix
If you do not need PZN and likeminds it is possible to disable both PZN and likeminds.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Version 7.0 , 8.0 and 8.5 * **************************************************************** * PROBLEM DESCRIPTION: A deadlock situation happened when * * two threads tried to acquire lock on * * instance of WsLogManager during * * startup * **************************************************************** * RECOMMENDATION: * **************************************************************** The likeminds thread first acquires a lock on the object com.ibm.ws.bootstrap.WsLogManager, it then attempts to acquire a lock on object java.util.logging.LogManager$LoggerContext but it is blocked by the server startup thread. Meanwhile the server.startup thread acquires a lock on object java.util.logging.LogManager$LoggerContext and is attempting to acquire a lock on object com.ibm.ws.bootstrap.WsLogManager and is blocked as the likeminds thread already has it.
Problem conclusion
To resolve the deadlock, an additional synchronized block has been added to minimize the situation where two threads try to acquire the same piece of code. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.31 , 8.0.0.9 , 8.5.5.2. 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
PI05410
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-11-04
Closed date
2014-01-30
Last modified date
2014-01-30
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
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022