PM41930: DEADLOCK CAN OCCUR IN FFDC WHEN A COMPONENT INVOKES FFDC WITHIN A LOGGING CALL

Fixes are available

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM41930: DEADLOCK CAN OCCUR IN FFDC WHEN A COMPONENT INVOKES FFDC WITHIN A LOGGING CALL

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?