IBM Support

PI71329: DeadLock detected in NodeAgent process during shutdown of node

Fixes are available

9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18

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.
    Caused
    due to
    
    
    [16. 10. 28   4:55:42:954 KST] 00000104 ServerStopped I
    ODCF0009I:
    ?????? ?? ???
    /cell/XYZ01Cell01/node/XYZ02Node02/server/nodeagent
    STOPPED(?)?
    ??: remote - markServerDown:
    XYZ01Cell01\XYZ02Node02\nodeagent
    [16. 10. 28   4:55:42:968 KST] 0000009e NGUtil$Server I
    ASND0003I:
    nodeagent ??? XYZNode02 ???? ??? ?? ??????.
    [16. 10. 28   4:55:43:328 KST] 000000b4 HAManagedItem I
    HAMI0024I:
    APC_Default ???? XYZCell01\XYZNode01\nodeagent
    [16. 10. 28   4:55:43:341 KST] 000000b4 HAManagedItem I
    HAMI0024I:
    HAWsmmControllerInterface_Default ????
    XYZ01Cell01\XYZ02Node01\nodeagent
    [16. 10. 28   4:55:44:411 KST] 000000b4 HAManagedItem I
    HAMI0024I:
    HAPluginCfgGeneratorInterface_Default ????
    XYZ01Cell01\XYZ02Node01\nodeagent
    [16. 10. 28   4:55:44:411 KST] 000000c1 HAManagedItem I
    HAMI0024I:
    INodeDetectConsumer_Default ????
    XYZ01Cell01\XYZ02Node01\nodeagent
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server WAS ND edition- Virtual              *
    *                  Enterprise/IM Component                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Server hangs during shutdown due to a   *
    *                      deadlock condition.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During jvm shutdown down a deadlock condition can occur between
    synchronized methods in com.ibm.ws.bbson.SubjectSubscriptionImpl
    and the singleton com.ibm.ws.bbson.BBFactoryImpl$MainMutex lock
    object which causes the shutdown down procedure to hang.
    

Problem conclusion

  • The synchronized methods in
    com.ibm.ws.bbson.SubjectSubscriptionImpl were removed and
    replaced with more fine-grained synchronized blocks, allowing
    for proper locking order to be maintained and avoiding the
    possibility of a deadlock condition occurring.
    
    The fix for this APAR is currently targeted for inclusion in fix
    packs 9.0.0.3 and 8.5.5.12.  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

    PI71329

  • 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

    2016-10-28

  • Closed date

    2016-12-08

  • Last modified date

    2016-12-08

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 November 2021