IBM Support

PK64992: DEADLOCK WHEN ROLLING OVER LOG FILES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If logging has been configured to roll over at a given size
    a deadlock can occur if the right conditions are met (cpu speed,
    server load, etc).
    
    For example, a trace is being gathered and logging has been
    configured to roll over at 50mb.  This problem can occur when
    the trace.log file has hit 50mb and tries to create a new
    trace.log.
    .
       The deadlock that occurs when this problem happens is this
    There is a deadlock detected:
         2LKDEADLOCKTHR  Thread "Non-Deferred Alarm Manager"
    (0x45F09B00)
    3LKDEADLOCKWTR    is waiting for:
    4LKDEADLOCKMON      sys_mon_t:0x456FF168 infl_mon_t: 0x456FF1A8:
    4LKDEADLOCKOBJ
    com/ibm/ejs/ras/SystemOutStream@013A9918/013A9924:
    3LKDEADLOCKOWN    which is owned by:
    2LKDEADLOCKTHR  Thread "MessageListenerThreadPool : 3"
    (0x4A182100)
    3LKDEADLOCKWTR    which is waiting for:
    4LKDEADLOCKMON      sys_mon_t:0x47443DB8 infl_mon_t: 0x47443DF8:
    4LKDEADLOCKOBJ      com/ibm/ejs/ras/Tr@45AF13F8/45AF1404:
    3LKDEADLOCKOWN    which is owned by:
    2LKDEADLOCKTHR  Thread "Non-Deferred Alarm Manager" (0x45F09B00)
    NULL
    .---------------------------------------------------------------
    .
    Thread 45F09B00
           at java/lang/Thread.run(Thread.java:810)
    3XMTHREADINFO      "Non-Deferred Alarm Manager" (TID:0x45F09B00,
    sys_thread_t:0x4569EA80, state:B, native ID:0x000012B4) prio=5
    4XESTACKTRACE          at
    com/ibm/ejs/ras/SystemOutStream.logMessage(SystemOutStream.java:
    286(Compiled Code))
    4XESTACKTRACE          at
    com/ibm/ejs/ras/SystemOutStream.processEvent(SystemOutStream.jav
    a:264(Compiled Code))
    4XESTACKTRACE          at
    com/ibm/ws/logging/WsHandlerWrapper.publish(WsHandlerWrapper.jav
    a:43(Compiled Code))
    4XESTACKTRACE          at
    java/util/logging/Logger.log(Logger.java:469(Compiled Code))
    4XESTACKTRACE          at
    com/ibm/ejs/ras/Tr.logToJSR47Logger(Tr.java:1612(Compiled Code))
    4XESTACKTRACE          at
    com/ibm/ejs/ras/Tr.fireEvent(Tr.java:1540(Compiled Code))
    4XESTACKTRACE          at
    com/ibm/ejs/ras/Tr.logJrasEvent(Tr.java:1187)
    4XESTACKTRACE          at
    com/ibm/ejs/ras/Tr.dispatchInternalEvents(Tr.java:1328)
    4XESTACKTRACE          at
    com/ibm/ejs/ras/Tr.entry(Tr.java:772(Compiled Code))
    4XESTACKTRACE          at
    com/ibm/ejs/util/am/AlarmThreadPool.fireAlarm(AlarmThreadPool.ja
    va:74(Compiled Code))
    4XESTACKTRACE          at
    com/ibm/ejs/util/am/AlarmManagerThread.run(AlarmManagerThread.ja
    va:122)
    4XESTACKTRACE          at java/lang/Thread.run(Thread.java:810)
    .--------------------------------------------------------------
    Thread  4182100:
    
     "MessageListenerThreadPool : 3" (TID:0x4A182100,
    sys_thread_t:0x474209F0, state:B, native ID:0x000014E8) prio=5
    4XESTACKTRACE          at
    com/ibm/ejs/ras/WrappingFileOutputStream.switchFiles(WrappingFil
    eOutputStream.java:565)
    4XESTACKTRACE          at
    com/ibm/ejs/ras/WrappingFileOutputStream.switchFiles(WrappingFil
    eOutputStream.java:508(Compiled Code))
    4XESTACKTRACE          at
    com/ibm/ejs/ras/WrappingFileOutputStream.incrementCount(Wrapping
    FileOutputStream.java:461(Compiled Code))
    4XESTACKTRACE          at
    com/ibm/ejs/ras/WrappingFileOutputStream.write(WrappingFileOutpu
    tStream.java:363(Compiled Code))
    4XESTACKTRACE          at
    java/io/PrintStream.write(PrintStream.java:446(Compiled Code))
    4XESTACKTRACE          at
    sun/nio/cs/StreamEncoder$ConverterSE.implWrite(StreamEncoder.jav
    a:284(Compiled Code))
    4XESTACKTRACE          at
    sun/nio/cs/StreamEncoder.write(StreamEncoder.java:194(Compiled
    Code))
    4XESTACKTRACE          at
    java/io/OutputStreamWriter.write(OutputStreamWriter.java:214(Com
    piled Code))
    4XESTACKTRACE          at
    java/io/BufferedWriter.flushBuffer(BufferedWriter.java:132(Compi
    led Code))
    4XESTACKTRACE          at
    java/io/BufferedWriter.write(BufferedWriter.java:233(Compiled
    Code))
    4XESTACKTRACE          at
    java/io/Writer.write(Writer.java:147(Compiled Code))
    4XESTACKTRACE          at
    java/io/PrintStream.write(PrintStream.java:491(Compiled Code))
    4XESTACKTRACE          at
    java/io/PrintStream.print(PrintStream.java:636(Compiled Code))
    4XESTACKTRACE          at
    java/io/PrintStream.println(PrintStream.java:773(Compiled Code))
    4XESTACKTRACE          at
    com/ibm/ejs/ras/SystemStream.writeWebSphereEvent(SystemStream.ja
    va:737(Compiled Code))
    4XESTACKTRACE          at
    com/ibm/ejs/ras/SystemOutStream.logMessage(SystemOutStream.java:
    286(Compiled Code))
    4XESTACKTRACE          at
    com/ibm/ejs/ras/SystemOutStream.processEvent(SystemOutStream.jav
    a:267(Compiled Code))
    4XESTACKTRACE          at
    com/ibm/ws/logging/WsHandlerWrapper.publish(WsHandlerWrapper.jav
    a:43(Compiled Code))
    4XESTACKTRACE          at
    java/util/logging/Logger.log(Logger.java:469(Compiled Code))
    4XESTACKTRACE          at
    com/ibm/ws/logging/WsLogger.deliverOrBuffer(WsLogger.java:244(Co
    mpiled Code))
    4XESTACKTRACE          at
    com/ibm/ws/logging/WsLogger.log(WsLogger.java:221(Compiled
    Code))
    4XESTACKTRACE          at
    com/ibm/ws/logging/WsLogger.logp(WsLogger.java:391(Compiled
    Code))
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V6.0.2 and V6.1                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: During log file rotation, a deadlock    *
    *                      may occur.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If logging has been configured to roll over at a given size
    a deadlock can occur if the right conditions are met (for
    example, CPU speed,server load, and so on).
    
    For example, a trace is being gathered and logging has been
    configured to roll over at 50mb.  This problem can occur when
    the trace.log file has hit 50mb and tries to create a
    newtrace.log.
    

Problem conclusion

  • Though this issue rarely presents itself, a lock has been
    added to the code to prevent this from happening.
    
    The fix for this APAR is currently targeted for inclusion in
    fixpacks 6.0.2.31 and 6.1.0.19.  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

    PK64992

  • Reported component name

    WEBSPH APP SERV

  • Reported component ID

    5724J0800

  • Reported release

    61S

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-04-24

  • Closed date

    2008-06-10

  • Last modified date

    2009-11-16

  • 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

    WEBSPH APP SERV

  • Fixed component ID

    5724J0800

Applicable component levels

  • R60S PSY

       UP

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

Document Information

Modified date:
29 December 2021