PI21768: DEADLOCK WHEN USING JAVA LOGGING FRAMEWORK

Fixes are available

APAR status

Closed as program error.

Error description

Your WebSphere AppServer JVM may hang and you may observe a
deadlock in javacore when using Java Logging Framework in
WebSphere Application Server V7.

For example you may see the many threads in javacore with the
following

java stack in the state: Deadlock/Blocked:
-----------------------------------
at
java/util/logging/LogManager.initializeGlobalHandlers(LogManager
.java:11 91(Compiled Code))
at
java/util/logging/LogManager.access$900(LogManager.java:135(Comp
iled Code))
at
java/util/logging/LogManager$RootLogger.getHandlers(LogManager.j
ava:1185 (Compiled Code))
at
sun/nio/cs/StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java
:355(Compiled Code))
at
sun/nio/cs/StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder
.java:425(Compiled Code))
at
sun/nio/cs/StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:
429(Compiled Code))
at
sun/nio/cs/StreamEncoder.flush(StreamEncoder.java:175(Compiled
Code))
at
java/io/OutputStreamWriter.flush(OutputStreamWriter.java:274(Com
piledCode))
at
org/apache/log4j/helpers/QuietWriter.flush(QuietWriter.java:58(C
ompiled Code))
at
org/apache/log4j/WriterAppender.subAppend(WriterAppender.java:31
6(Compiled Code))
at
org/apache/log4j/WriterAppender.append(WriterAppender.java:160(C
ompiled Code))
at
org/apache/log4j/AppenderSkeleton.doAppend(AppenderSkeleton.java
:251(Com
...
...
...
.
The defect was reported in WebSphere V7.0.0.31

Local fix

```
N/A.
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: Excessive System.out statements in an   *
*                      application interfere with              *
*                      Application Server's logging            *
*                      framework and causes a deadlock         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Customer application is using excessive System.out, which
at some point of time interferes with WebSphere Application
server's logging framework and causes a deadlock.

Problem conclusion

The logging framework has been updated to avoid the deadlock.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.35, 8.0.0.10 and 8.5.5.5.
Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

1) Customer can disable the system.out.println statement form
the console.
2) Disable the logging from WsLoggerConfigurator class by
setting log trace specification as
"com.ibm.ws.logging.WsLoggerConfigurator=off"

Comments

APAR Information

APAR number
PI21768
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
2014-07-10
Closed date
2014-09-25
Last modified date
2014-09-25

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z 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:
12 January 2022

Tips

PI21768: DEADLOCK WHEN USING JAVA LOGGING FRAMEWORK

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

Document Information

Share your feedback

Need support?