IBM Support

PI24847: NODEAGENT MIGHT NOT START APPLICATION SERVER AFTER SYSTEM REBOOT BECAUSE OF WRONG PID INFO IN MONITOR.STATE

Fixes are available

7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Nodeagent starts application servers automatically after system
    reboot if monitor policy is set. When nodeagent trie to start
    appserver, WebSphere will check if the <appserver>.pid file is
    present and the pid is running.  Also WAS looks into
    monitor.state file to see the appserver PID in the file is
    running or not.
    The PID info in monitor.state is updated everytime managed
    appserver started/stopped. However if the PID info in
    monitor.state was not updated unexpectedly,  this might cause
    automatic appserver start up failure.
    
    We have similar APAR PM89648. In PM89648, we fixed the error
    case for checking the .pid file. In this APAR, we fixed the
    error case for the monitor.state file
    

Local fix

  • Removing monitor.state file manually after all java process are
    stopped.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server, Network Deployment edition.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Application servers configured to be    *
    *                      automatically restarted by node agent   *
    *                      might not be consistently restarted.    *
    ****************************************************************
    * RECOMMENDATION:  Install a Fix Pack containing this APAR.    *
    ****************************************************************
    During the node agent startup process, a search is done for
    the PID files (and monitor.state file) of application servers
    that are being managed. If the PID file (or monitor.state) is
    present and the PID is alive in the system process list, it is
    assumed  that the  application server is running and it is not
    necessary to restart it.
    In certain circumstances, that logic can be incorrect, as some
    other live process can acquire the PID that used to be held by
    an appserver. In such cases, the application server restart
    might not occur.
    

Problem conclusion

  • The code has been modified to check the communication with the
    application server processes that are candidates for
    restarting.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.37, 8.0.0.11 and 8.5.5.5.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Start the server manually.
    

Comments

APAR Information

  • APAR number

    PI24847

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-08-29

  • Closed date

    2014-12-02

  • Last modified date

    2015-03-30

  • 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

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PI24847

Modified date: 30 March 2015