IBM Support

PI44409: SERVER TAKES A LONG TIME TO START THROUGH THE ADMINISTRATIVE CONSOLE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • In this case, a START command is not used to start the server,
    rather a command used by an automation product that the server
    is starting through automation so the product correctly reports
    the server up or down state.  When this happens, the node agent
    is not able to monitor that the server has actually started and
    report this status to the dmgr to then report this via the
    admin console.  The server does start ok.
    
    The node agent will show this message:
    ADMN1000I: An attempt is made to launch AppServer on node
    
    Shortly followed by this FFDC:
    FFDC Exception:com.ibm.ws.process.exception.ProcessOpException
    SourceId:com.ibm.ws.process.WS390ProcessImpl.id ProbeId:186
    Reporter:com.ibm.ws.process.WS390ProcessImpl@777b36b9
    com.ibm.ws.process.exception.ProcessOpException: Invalid
    process object.  nativeHandle (mvsToken) is 'null'
     at com.ibm.ws.process.WS390ProcessImpl.
    checkNativeHandle(WS390Proce ssImpl.java:742)
     at com.ibm.ws.process.WS390ProcessImpl.
    id(WS390ProcessImpl.java:499 )
     at com.ibm.ws.management.nodeagent.NodeAgent.
    launchProcessPrivate(N odeAgent.java:1376)
    
    Then about 10 minutes later, this FFDC:
    FFDC Exception:java.net.SocketTimeoutException
    SourceId:com.ibm.ws.management.nodeagent.NodeAgent.waitForServer
    Init ProbeId:368
    Reporter:com.ibm.ws.management.nodeagent.NodeAgent@38608807
    java.net.SocketTimeoutException: Accept timed out
     at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:480)
     at java.net.ServerSocket.implAccept(ServerSocket.java:479)
     at java.net.ServerSocket.accept(ServerSocket.java:447)
     at com.ibm.ws.management.nodeagent.NodeAgent.
    waitForServerInit(Node Agent.java:1811)
    
    And this error message:
    ADML0040E: The process timed out waiting for server "AppServer"
    initialization: 600 seconds
    

Local fix

  • use the START command to start the server from the admin console
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0, and V8.5                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
    *                      will hang when starting an application  *
    *                      server from the Administrative Console  *
    *                      with a custom START command that does   *
    *                      not begin with "START".                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The Admin Console allows a user to specify a custom START
    command. If this custom START command does not begin with
    "START", when an attempt is made to start an application server
    from the Administative Console, instead of the starting, the
    server will hang and a message like this may be issued in the
    node agent job log:
    BBOO0221W: ADML0040E: The process timed out waiting for
    server "<server name>" initialization: 600 seconds
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI44409

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-07-06

  • Closed date

    2015-08-05

  • Last modified date

    2015-11-03

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

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

    PI46371

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 850

Reference #: PI44409

Modified date: 03 November 2015