If JRE update is run without first manually stopping the Tomcat service, Tomcat will no longer start after the next time it is stopped. This most often happens after rebooting per the JRE installer's request.
To reproduce the error
- Install the latest Tomcat 7 as a Windows service with Java 6 u29 installed. Tomcat should run just fine.
- Update to Java 6u31 without first stopping the Tomcat service. Java requires a server reboot and after the reboot the Tomcat service will no longer start.
Logs following reboot
Tomcat 7 stdout
2012-04-03 12:25:02 Commons Daemon procrun stdout initialized 2012-04-03 12:42:25 Commons Daemon procrun stdout initialized Error occurred during initialization of VM java/lang/NoClassDefFoundError: java/lang/Object
Last part of Tomcat7 stderr (the only line after the Java update and restart)
2012-04-03 12:42:25 Commons Daemon procrun stderr initialized