IBM Support

PI77254: DMGR or Node Agent times out during shutdown issuing AdminException ADMU3060E

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The hang on shutdown is due to a wait for initialization
    call
    being made by the IM_REST services running the dmgr and
    nodeagent processes. It's hanging because the P2P layer is
    not
    successfully initializing on the dmgr process.
    Regardless of the state of P2P , dmgr or nodeagent should
    not
    be hanging on shutdown.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server WAS ND edition- Virtual              *
    *                  Enterprise/IM Component                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: DMGR or Node Agent times out during     *
    *                      shutdown issuing AdminException         *
    *                      'ADMU3060E: Timed out waiting for       *
    *                      server shutdown.'.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The Deployment Manager or Node Agent process times out during
    server shutdown issuing the following AdminException in
    SystemOut.log:
    ADMU3111E: Server stop requested but failed to complete.
    ADMU3002E: Exception attempting to process server dmgr
    ADMU3007E: Exception
    com.ibm.websphere.management.exception.AdminException:
    ADMU3060E: Timed out waiting for server shutdown.
    ADMU3007E: Exception
    com.ibm.websphere.management.exception.AdminException:
    ADMU3060E: Timed out waiting for server shutdown.
     at
    com.ibm.ws.management.tools.WsServerStop.runTool(WsServerStop.ja
    va:434)
     at
    com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.j
    ava:271) ...
    
    Associated javacores taken while the server shutdown routine is
    hung will show a single running daemon thread waiting on
    'com/ibm/ws/wsgroup/nd/odc/ODCGroup' with the following stack:
    Java callstack:
     at java/lang/Object.wait(Native Method)
     at java/lang/Object.wait(Object.java:167(Compiled Code))
     at
    com/ibm/ws/wsgroup/nd/odc/ODCGroup.waitUntilReady(ODCGroup.java:
    278)
      (entered lock:
    com/ibm/ws/wsgroup/nd/odc/ODCGroup@0x0000000001A77FD8, entry
    count: 1)
     at
    com/ibm/ws/xd/agent/odc/rest/ODCServer.startService(ODCServer.ja
    va:506)
      (entered lock:
    com/ibm/ws/xd/agent/odc/rest/ODCServer@0x0000000001E668A0, entry
    count: 1)
     at
    com/ibm/ws/xd/agent/odc/XDAgentODCService$IMServiceStateChange.r
    un(XDAgentODCService.java:193)
    

Problem conclusion

  • The Intelligent Management (IM) REST service, residing on the
    deployment manager and node agents, must wait until ODCGroup is
    up and healthy before accepting requests to avoid sending out
    partial routing information to its clients. However ODCGroup
    will never initialize if the P2P/SON communication layer fails
    to start and under that condition the IM REST service logic
    allowed the shutdown process on the deployment manager and node
    agents to hang. The IM REST service ODCGroup wait for
    initialization logic has been altered to prevent the hang
    condition on shutdown when the P2P/SON layer fails start-up.
    
    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

    PI77254

  • 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-02-27

  • Closed date

    2017-03-08

  • Last modified date

    2017-03-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":"BU048","label":"IBM Software"},"Product":{"code":"SSCVS22","label":"General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
08 March 2017