IBM Support

IZ90072: THREAD DEADLOCK CAUSES APPLICATION SERVER CRASH

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Random UI's are crashing due to a thread deadlock, the following
    is the deadlock shown in the thread dump.
    
    1LKDEADLOCK    Deadlock detected !!!
    NULL           ---------------------
    NULL
    2LKDEADLOCKTHR  Thread "Thread-121645" (0x000000012657AF00)
    3LKDEADLOCKWTR    is waiting for:
    4LKDEADLOCKMON      sys_mon_t:0x0000000124AFB850 infl_mon_t:
    0x0000000124AFB8A0:
    4LKDEADLOCKOBJ
    psdi/webclient/beans/workorder/ActivityAppBean@070000001A4CC228/
    070000001A4CC240:
    3LKDEADLOCKOWN    which is owned by:
    2LKDEADLOCKTHR  Thread "WebContainer : 5" (0x000000011C599200)
    3LKDEADLOCKWTR    which is waiting for:
    4LKDEADLOCKMON      sys_mon_t:0x0000000124A4E070 infl_mon_t:
    0x0000000124A4E0C0:
    4LKDEADLOCKOBJ
    psdi/webclient/system/beans/ResultsBean@070000001A4CF6F0/0700000
    01A4CF708:
    3LKDEADLOCKOWN    which is owned by:
    2LKDEADLOCKTHR  Thread "Thread-121645" (0x000000012657AF00)
    
    Maximo logs show WORKORDERSPEC mboset using a large amount of
    memory as well as the time of the deadlock
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Async Dialogs , or operation can cause  *
    *                      this situation                          *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    Async Dialogs , or operation can cause this situation
    

Problem conclusion

  • Fix the code which can Enable Async on processing of the
    request and and disable once done and during finalization
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ90072

  • Reported component name

    MAXIMO INSTALL

  • Reported component ID

    5724R46IT

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-12-02

  • Closed date

    2010-12-03

  • Last modified date

    2010-12-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • MAXIMO
    

Fix information

  • Fixed component name

    MAXIMO INSTALL

  • Fixed component ID

    5724R46IT

Applicable component levels

  • R710 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCHPMC","label":"Maximo Install Tool"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
06 September 2022