Fixes are available
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
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
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
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.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
The logging of a WSSecurityException exception also invokes FFDC in the printStackTrace method. This caan cause a deadlock as follows when other components are trying to invoke FFDC as in the example shown below: Deadlock in FFDC components. WebSphere Application Server V7.0.0.13. Distributed operating Systems. ***** 1LKDEADLOCK Deadlock detected !!! NULL --------------------- NULL 2LKDEADLOCKTHR Thread "WebContainer : 397" (0x0000000004EBF600) 3LKDEADLOCKWTR is waiting for: 4LKDEADLOCKMON sys_mon_t:0x00000200283F76E0 infl_mon_t: 0x00000200283F7750: 4LKDEADLOCKOBJ com/ibm/ws/ffdc/impl/FfdcProvider@0x00000000815FE578/0x000000008 15FE584: 3LKDEADLOCKOWN which is owned by: 2LKDEADLOCKTHR Thread "WebContainer : 393" (0x0000000005103000) 3LKDEADLOCKWTR which is waiting for: 4LKDEADLOCKMON sys_mon_t:0x00000200246B3890 infl_mon_t: 0x00000200246B3900: 4LKDEADLOCKOBJ com/ibm/ejs/ras/SystemOutStream@0x00000000810E0830/0x00000000810 E083C: 3LKDEADLOCKOWN which is owned by: 2LKDEADLOCKTHR Thread "WebContainer : 397" (0x0000000004EBF600) Where the stacks of those 2 threads show: 3XMTHREADINFO "WebContainer : 397" J9VMThread:0x0000000004EBF600, j9thread_t:0x000002002E15C290, java/lang/Thread:0x0000000140090AA0, state:B, prio=5 3XMTHREADINFO1 (native thread ID:0x3B44, native priority:0x5, native policy:UNKNOWN) 3XMTHREADINFO2 (native stack address range from:0x0000020037C00000, to:0x0000020037C40000, size:0x40000) 3XMTHREADINFO3 Java callstack: 4XESTACKTRACE at com/ibm/ffdc/util/provider/FfdcProvider.getIncident(FfdcProvider .java:66 (Compiled Code)) 4XESTACKTRACE at com/ibm/ffdc/util/provider/Ffdc.<init>(Ffdc.java:60(Compiled Code)) 4XESTACKTRACE at com/ibm/ffdc/util/provider/FfdcProvider.getFfdc(FfdcProvider.jav a:289(Co mpiled Code)) 4XESTACKTRACE at com/ibm/ffdc/util/provider/FfdcProvider.log(FfdcProvider.java:29 8) 4XESTACKTRACE at com/ibm/ffdc/impl/Ffdc.log(Ffdc.java:221) 4XESTACKTRACE at com/ibm/websphere/security/WSSecurityException.printStackTrace(W SSecurit yException.java:242) 3XMTHREADINFO "WebContainer : 393" J9VMThread:0x0000000005103000, j9thread_t:0x0000020032F63070, java/lang/Thread:0x0000000140090CC0, state:B, prio=5 3XMTHREADINFO1 (native thread ID:0x3B36, native priority:0x5, native policy:UNKNOWN) 3XMTHREADINFO2 (native stack address range from:0x0000020013400000, to:0x0000020013440000, size:0x40000) 3XMTHREADINFO3 Java callstack: 4XESTACKTRACE at com/ibm/ejs/ras/SystemOutStream.logMessage(SystemOutStream.java: 300(Comp iled Code)) 4XESTACKTRACE at com/ibm/ejs/ras/SystemOutStream.processEvent(SystemOutStream.jav a:278(Co mpiled Code)) 4XESTACKTRACE at com/ibm/ws/logging/WsHandlerWrapper.publish(WsHandlerWrapper.jav a:43(Com piled Code)) 4XESTACKTRACE at java/util/logging/Logger.log(Logger.java:1109(Compiled Code)) 4XESTACKTRACE at com/ibm/ws/logging/WsLogger.deliverOrBuffer(WsLogger.java:265(Co mpiled Code)) 4XESTACKTRACE at com/ibm/ws/logging/WsLogger.log(WsLogger.java:230(Compiled Code)) 4XESTACKTRACE at com/ibm/ws/logging/WsLogger.logp(WsLogger.java:479(Compiled Code))
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 and V8.0 * **************************************************************** * PROBLEM DESCRIPTION: Combining a RAS services logging and * * FFDC invocation can result in a * * deadlock. * **************************************************************** * RECOMMENDATION: * **************************************************************** Generally, components should be invoking RAS services and FFDC components separately. However, in this particular case, the component is used as an API and needed a mechanism for tracking the exceptions with FFDC.
Problem conclusion
FFDC loggers have been configured to be asynchronous to avoid the deadlock. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.21 and 8.0.0.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
PM41930
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-06-17
Closed date
2011-09-02
Last modified date
2011-09-02
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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
27 October 2021