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

8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
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
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
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
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

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 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