PI71530: WSLOGMANAGER DEADLOCK

Fixes are available

APAR status

Closed as program error.

Error description

Deadlock detected in  [WorkManager.bpm-em-workmanager : 31]
[WorkManager.bpm-em-workmanager : 25]  where

WorkManager.bpm-em-workmanager : 25
Owns Monitor Lock on
com/ibm/rmi/util/Utility$RemoteToTieClassCache@0x000000010104FB5
8 ,
org/eclipse/core/runtime/adaptor/EclipseLog@0x0000000102434B10 ,
com/ibm/wsspi/container/binding/sca/remote/EJSRemoteCSLDepartmen
tAllocat
ionHome_5cdf82f1@0x0000000195A33628
Waiting for Monitor Lock on
com/ibm/ws/bootstrap/WsLogManager@0x0000000101B8AFC8

and

WorkManager.bpm-em-workmanager : 31:
Owns Monitor Lock on
com/ibm/ws/bootstrap/WsLogManager@0x0000000101B8AFC8 ,
com/ibm/ws/monitoring/policy/data/EventSourceImpl@0x0000000195A3
B138
Waiting for Monitor Lock on
org/eclipse/core/runtime/adaptor/EclipseLog@0x0000000102434B10

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server.                                     *
****************************************************************
* PROBLEM DESCRIPTION: A deadlock may occur on the             *
*                      WsLogManager object between multiple    *
*                      threads, when the WebSphere             *
*                      Application Server and an application   *
*                      are both logging at the same time.      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In the WsLogManager.getLogger() method, if the logger is null,
a thread goes into a synchronized block to create a new
instance of WsLogger object, thus locking the WsLogManager
object. Meanwhile, another logging thread, will try to contend
for the WsLogManager, causing a never-ending wait condition,
leading to a deadlock.
Below is the snippet of the stack trace, when the deadlock
occurs on the WsLogManager object:
Deadlock detected in  [WorkManager.bpm-em-workmanager : 31]
[WorkManager.bpm-em-workmanager : 25]  where
WorkManager.bpm-em-workmanager : 25
Owns Monitor Lock on
com/ibm/rmi/util/Utility$RemoteToTieClassCache@0x000000010104FB
58 ,
org/eclipse/core/runtime/adaptor/EclipseLog@0x0000000102434B10,
com/ibm/wsspi/container/binding/sca/remote/EJSRemoteCSLDepartme
ntAllocationHome_5cdf82f1@0x0000000195A33628
Waiting for Monitor Lock on
com/ibm/ws/bootstrap/WsLogManager@0x0000000101B8AFC8
...
and
WorkManager.bpm-em-workmanager : 31:
Owns Monitor Lock on
com/ibm/ws/bootstrap/WsLogManager@0x0000000101B8AFC8 ,
com/ibm/ws/monitoring/policy/data/EventSourceImpl@0x00000001953
B138
Waiting for Monitor Lock on
org/eclipse/core/runtime/adaptor/EclipseLog@0x0000000102434B10
...

Problem conclusion

To prevent the deadlock situation from happening, the code was
re-structured, so the threads do not hold a lock on the
WsLogManager object, when creating a new WsLogger object.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.43, 8.0.0.14, 8.5.5.12, 9.0.0.3.  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
PI71530
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
2016-10-31
Closed date
2016-12-13
Last modified date
2016-12-13

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
R900 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":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI71530: WSLOGMANAGER DEADLOCK

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

R850 PSY

R900 PSY

Document Information

Share your feedback

Need support?