Make a note of this service name (not case sensitive). Find your Tomcat service: In the list of services, find the name of the Apache Tomcat service with a status of “Stopping”.Open Task Manager: + +, then click “Task Manager” then click on the “Services” tab.

You could restart your machine if you like, but sometimes this is not possible or ideal (especially if on a production server).Ī quick way around it that I am recording for my own benefit mostly: I have no idea why it does this, but I haven’t the enthusiasm to explore. It’s not something I need to do often, but when I do, the Tomcat service seems to hang in a status of “Stopping” for at least 10 minutes. It's a shame that the automated JDK update facility provided by Java breaks our application.Apache takes a silly amount of time to stop its service.

Sometimes even that fails, though, with the message 'The jar-file 'reach-stream-installer-izpack.jar' could not be executed.' (IzPack being the automated installer tool we use). (1) usually works for us because we have an installer for the app which will also install a clean version of Java if required. We have found two workarounds: (1) reinstall the app (2) reinstall Java. If you get the noclassdeffound error for java/lang/Object, it's a pretty good bet that the combination of a JDK upgrade with a long-running Java app has left you with a corrupt JDK/JRE. One symptom of this is to open a command window and type 'java -version'. But if there's a long-running Java app running at the same time as the update is taking place, that app will have various Java libs and exe's (like the main jre.exe) locked, and the Java update fails. There might be one or two renames left to do when the install finishes, and those renames are supposed to happen after a reboot. We create it as a Windows service with the 'procrun' mechanism in Apache Commons Daemon, which is the same way the Tomcat Windows service works.įrom hints of other reports of this, it seems like the Java update process moves/renames files as part of upgrading to the new version. We have observed this with a long-running (but not Tomcat) Java app that runs as a Windows service.

Apache tomcat 8 service windows restart