Fixes are available
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Windows WASService generates intermittent Application Event 109, "Could not determine the process id of the java process" on startup and fails to start. WASService sometimes tries to read .pid file before new created java process write PID number in the file. This timing gap causes failure of a server process to start.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM Websphere Application Server customers * * that have configured the Application Server or Deployment * * Manager to run as a Windows Service * **************************************************************** * PROBLEM DESCRIPTION: Windows WASService generates * * intermittent Application Event 109, "Could not determine * * the process if of the java process" on startup and fails to * * start. WASService sometimes tries to read the .pid file * * before new created java process write PID number in the file.* * This timing gap causes failure of a server process to start. * **************************************************************** * RECOMMENDATION: Apply this fix * **************************************************************** * before new created java process write PID number in the file.* * This timing gap causes failure of a server process to start. * **************************************************************** * RECOMMENDATION: Apply this fix * ****************************************************************
Problem conclusion
WASService.exe was updated
Temporary fix
Comments
APAR Information
APAR number
PK52495
Reported component name
WEBSPH APP SERV
Reported component ID
5724J0800
Reported release
60W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-09-10
Closed date
2007-09-12
Last modified date
2007-10-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
WASSVC
Fix information
Fixed component name
WEBSPH APP SERV
Fixed component ID
5724J0800
Applicable component levels
R60W PSY
UP
R61W PSY
UP
Document Information
Modified date:
29 December 2021