Windows Service Corruption Can Cause WebSphere Application Server Not To Start
MicheleCalcavecchia 270000HCF1 Comments (3) Visits (8660)
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:
If the server starts normally when it is not associated with the Windows Service, the problem is in the Windows Service.