IBM Support

PI43678: APPLICATION SERVER FAIL TO START IF OLD PID FILE EXIST AND BEING USED BY OTHER PROCESS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Application server fails to start if old pid file exists and
    the same pid is being used by some other process. There is no
    indication in the logs. In this case application server was
    not stopped gracefully or crashed, the PID file stays there
    and some other process occupying the same PID value causes
    application server to fail to start with no errors or failure
    information in the logs.
    

Local fix

  • Ø
    Delete old pid file and start jvm
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users      *
    *                  using Microsoft Windows Services            *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using Microsoft Windows services   *
    *                      to start the application server, the    *
    *                      start may fail if prior shutdown was    *
    *                      not clean.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When WebSphere Application Server is stopped, it moves a file
    indicating its process id (pid). If this file is not removed
    and if another process happens to start with the same pid, the
    service will think Application Server is already running and
    will not attempt to start it.
    

Problem conclusion

  • Added code to check the program name if a pid file is found
    and an application is running with that pid. If the
    application is not java, it is assumed this is not WebSphere
    Application Server and the old pid file is removed and the
    start process proceeds.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.12 and 8.5.5.7.  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

    PI43678

  • 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

    2015-06-24

  • Closed date

    2015-06-29

  • Last modified date

    2015-06-29

  • 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

  • R800 PSY

       UP

  • 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:
28 April 2022