IBM Support

PH03333: DEADLOCK SITUATION IN DEFAULTWORKMANAGER:ALARMMANAGER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A deadlock situation may happen with the
    DefaultWorkManager.AlarmManager and Async bean threads The
    deadlock situation is as following:
    
    
    ***WARNING*** Deadlock detected in
    [DefaultWorkManager:AlarmManager] [Thread-75]
    
    Here are the details:
    
    Thread Name: DefaultWorkManager:AlarmManager
    State: Deadlock/Blocked
    
    Monitor:
    Owns Monitor Lock on
    com/ibm/ws/util/BinaryHeap@0x0000000703F64400
    
    Waiting for Monitor Lock on
    com/ibm/ws/asynchbeans/am/_Alarm@0x000000070D283070
    
    Java Stack:
    at
    com/ibm/ws/asynchbeans/am/AlarmManagerThread.run(AlarmManagerThr
    ead.java:123)
    
    
    The other thread shows:
    
    Thread Name: Thread-75
    State: Deadlock/Blocked
    
    Monitor:
    Owns Monitor Lock on
    com/ibm/ws/asynchbeans/am/_Alarm@0x000000070D283070 ,
    java/lang/Object@0x0000000705439170
    
    Waiting for Monitor Lock on
    com/ibm/ws/util/BinaryHeap@0x0000000703F64400
    
    Java Stack:
    at
    com/ibm/ws/asynchbeans/am/AlarmManager.cancel(AlarmManager.java:
    470)
    at com/ibm/ws/asynchbeans/am/_Alarm.cancel(_Alarm.java:202)
    at com/ibm/ws/asynchbeans/AlarmImpl.cancel(AlarmImpl.java:385)
    at
    com/ibm/correlation/engine/util/scheduler/EventProcessorTimer.ad
    dWakeUp(EventProcessorTimer.java:221)
    at com/ibm/correlation/rules/WakeableSMRule.newWakeUp(Bytecode
    PC:61)
    at
    com/ibm/correlation/rules/WakeableSMRule.startTimerAt(Bytecode
    PC:87)
    at com/ibm/correlation/rules/WakeableSMRule.startTimer(Bytecode
    PC:33)
    at
    com/ibm/correlation/rules/Sequence.postMatchedEventProc(Bytecode
    PC:45)
    at
    com/ibm/correlation/rules/Sequence.patternProcessEvent(Bytecode
    PC:138(Compiled Code))
    at
    com/ibm/correlation/rules/AbstractRule.doProcessEvent(Bytecode
    PC:171(Compiled Code))
    at
    com/ibm/correlation/rules/CloneManager.patternProcessEvent(Bytec
    ode PC:385(Compiled Code))
    at
    com/ibm/correlation/rules/CloneManager.doProcessEvent(Bytecode
    PC:76(Compiled Code))
    at
    com/ibm/correlation/rules/CloneManager.doProcessEvent(Bytecode
    PC:4(Compiled Code))
    at
    com/ibm/correlation/rules/AbstractRule$EventProcessor.impl(Bytec
    ode PC:6(Compiled Code))
    at
    com/ibm/correlation/rules/AbstractRule$EventProcessor.processEve
    nt(Bytecode PC:88(Compiled Code))
    at
    com/ibm/correlation/engine/persistence/PersistenceEngine.dispatc
    hEvent(Bytecode PC:278)
    at
    com/ibm/correlation/engine/persistence/PersistenceEngine.doProce
    ssEvent(Bytecode PC:135)
    at
    com/ibm/correlation/engine/persistence/PersistenceEngine.process
    Event(Bytecode PC:101)
    at
    com/ibm/tws/event/EventProcessorManager.processEvent(EventProces
    sorManager.java:651)
    ...
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Deadlock in Asynchronous Beans Alarm    *
    *                      Manager                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The Asynchronous Beans Alarm Manager can deadlock when the
    system property,
    com.ibm.ws.asynchbeans.am.clearAlarmQueue, is set to true.
    

Problem conclusion

  • Fixed the code to avoid deadlock when the system property,
    com.ibm.ws.asynchbeans.am.clearAlarmQueue, is set to true.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.15.  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

    PH03333

  • 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

    2018-09-28

  • Closed date

    2018-12-10

  • Last modified date

    2018-12-10

  • 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

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 October 2021