After Java is updated, Management Console deployed in Tomcat doesn't start.
When the Tomcat Windows service is started an error is displayed:
In Event Viewer you can find an Error with event ID 7024 from Service Control Manager:
"The <Service_Name> service terminated with service-specific error Incorrect function"
The better message can be found in Tomcat's common_daemon log:
[info] [ 304] Starting service...
[error] [ 304] Failed creating Java <java path>\bin\server\jvm.dll
[error] [ 304] The system cannot find the path specified.
[error] [ 304] ServiceStart returned 1
The path to jvm.dll is no longer valid. Tomcat most probably points to the old Java path, before the upgrade.
When Tomcat is installed as a windows service follow the steps below to resolve:
- From Start > Programs open Configure Tomcat application (from the Tomcat program group)
- Go to the Java tab
- Under "Java Virtual Machine" click the "..." button, browse to the new location of jvm.dll (under the new java version location) and select it.
- Click OK to save
- Start the Tomcat service
If Tomcat is running in command mode the JAVA_HOME or JRE_HOME environment variable needs to be pointed to the new Java location before Tomcat is restarted.
Level of Complexity
Add any references to other internal or external articles