IBM Support

PM53578: AT NODE AGENT STARTUP, THE NODE AGENT STARTS THE WEBSERVER WHEN IT SHOULD NOT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If the node agent is stopped before the webserver, then when the
    node agent restarts, it will start the webserver.  This is
    because the node agent creates a default monitoring policy for
    webservers since these servers do not have one defined.  For
    this type of server a value of STOPPED should be used for
    nodeRestartState rather than the default of PREVIOUS.
    

Local fix

  • Stop the webserver before the node agent is stopped
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Network Deployment V7.0 on z/OS      *
    ****************************************************************
    * PROBLEM DESCRIPTION: At nodeagent startup, the nodeagent     *
    *                      starts the webserver when it should     *
    *                      not.                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During nodeagent startup, it checks the monitoring policy of
    servers on its node. A webserver or Generic server use the
    default monitoring policy which has a NodeRestartState of
    PREVIOUS. If the webserver was running at the time the
    nodeagent was stopped, the nodeagent saves that fact for when
    the nodeagent is restarted.  At nodeagent restart with the
    NodeRestartState of the webserver as PREVIOUS, the previous
    state of the webserver was saved as STARTED, so the nodeagent
    restarts the webserver. If the webserver is not running when
    the nodeagent is stopped, then at nodeagent restart, the
    nodeagent  will not try to start the webserver because the
    previous state of the webserver was saved as STOPPED.
    

Problem conclusion

  • The nodeagent code was modified for webserver or generic
    server on z/OS to have a NodeRestartState of STOPPED.
    So regardless of the webserver's previous state, the nodeagent
    will not try to start it.
    
    APAR PM53578 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.23 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM53578

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-12-05

  • Closed date

    2012-02-06

  • Last modified date

    2012-06-03

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

    PM51744

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

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK78616

       UP12/05/26 P F205

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022