Technical Blog Post
Windows Service Corruption Can Cause WebSphere Application Server Not To Start
Perhaps you've run into this scenario: The Windows Service states the JVM process is started but WebSphere Application Server does not start. The SystemOut.log shows no entries in the log, the startServer.log shows that the JVM is waiting on initialization indefinitely. Windows task manager may show that a Java™ process is consuming high CPU but the Process ID (PID) does not match any of the server PIDs.
To check if the Windows Service is the problem:
- Make sure that all the java processes are stopped.
- Clean up all the logs, wstemp, temp and config/temp locations.
- Clean up the contents of the javasharedresources directory.
- Remove the windows service associated with the JVM process using the tool provided in this link:
IBM Using WASServiceCmd to create Windows services for WebSphere Application Servers
- Start the JVM from the command line and confirm that it starts normally.
If the server starts normally when it is not associated with the Windows Service, the problem is in the Windows Service.
- Stop the server and re-add the windows service.
- Try to start the JVM using the Windows services this time.
- Why does logging off of Windows system crash WebSphere Application Server? - dWAnswers
- WebSphere Application Server process exits without leaving a footprint in log files or no core dumps
- Using the WASServiceHelper utility to create Windows services for application servers
- How to clear the WebSphere class caches