IBM Support

PI74450: Deadlock detected in NodeAgent process during shutdown of node

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DeadLock detected in NodeAgent process during shutdown:
    
    Deadlock detected !!!
    ---------------------
    
    Thread "Non-deferrable Alarm : 2" (0x000000003187D400)
    is waiting for:
    sys_mon_t:0x000001002DCEF0E8 infl_mon_t:
    0x000001002DCEF130:
    com/ibm/son/mesh/Peer@0x00000000823C1D00
    which is owned by:
    Thread "sonOutThreadPool : 14" (0x0000000031947100)
    which is waiting for:
    sys_mon_t:0x000001002D660138 infl_mon_t:
    0x000001002D660180:
    com/ibm/ws/bbson/BBFactoryImpl$MainMutex@0x00000000823E2F40
    which is owned by:
    Thread "Non-deferrable Alarm : 2" (0x000000003187D400)
    
    We can see that the thread "Non-deferrable Alarm : 2" owned
    lock
    com/ibm/ws/bbson/BBFactoryImpl$MainMutex@0x00000000823E2F40
    and waiting for lock
    com/ibm/son/mesh/Peer@0x00000000823C1D00
    which is owned by "sonOutThreadPool : 14".  At same time,
    "sonOutThreadPool : 14" is also waiting for the lock owned
    by
    "Non-deferrable Alarm : 2". Both of the two threads didn't
    release the lock and are waiting for the other lock.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Network Deployment edition           *
    ****************************************************************
    * PROBLEM DESCRIPTION: Deployment Manager or Node Agent        *
    *                      processes are observed to hang during   *
    *                      normal shutdown.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The shutdown sequence of Deployment Manager or Node Agent
    processes hang due to a deadlock between mutex objects
    com/ibm/ws/bbson/BBFactoryImpl$MainMutex and
    com/ibm/son/mesh/Peer. The deadlock is due to a timing window
    during shutdown when components are closing out their BBSON
    bulletin board subscriptions as the bulletin boards themselves
    are being closed.
    

Problem conclusion

  • This deadlock issue was addressed by adding yet another mutex,
    com.ibm.ws.bbson.SubjectSubscriptionImpl.SUB_CLOSE_LOCK, which
    must be obtained prior initiating closure of either a subject
    subscription or an entire bulletin board.
    
    The fix for this APAR is currently targeted for inclusion in fix
    packs 8.5.5.12 and 9.0.0.4.  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

    PI74450

  • 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

    2017-01-05

  • Closed date

    2017-04-12

  • Last modified date

    2017-04-12

  • 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

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

Document Information

Modified date:
06 September 2021