IBM Support

PI21768: DEADLOCK WHEN USING JAVA LOGGING FRAMEWORK

Fixes are available

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

Subscribe

You can track all active APARs for this component.

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

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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PI21768

Modified date: 25 September 2014