Linux – Tomcat – How to stop, start, restart

javalinuxtomcat

I installed Tomcat7 from source on a debain. However, based on the information online I should be able to start and stop the service using the following command:

service tomcat7 stop/start

However when I run this, I get this error:

tomcat7: unrecognized service

Can anyone tell me please how I can make it so Tomcat can be stopped and started.

Best Answer

You've installed Tomcat from source, and the Tomcat source package does not provide a service script for Debian. Tomcat works on a number of platforms and rather than trying to maintain the appropriate service startup configuration for Debian/RedHat/Solaris/AIX/Mac OS/Windows, they leave that up to the people who develop packages for your particular OS and distribution.

If Tomcat 7 is already packaged for Debian, your best bet is simply using the available package rather than building your own.

Alternatively, you can obtain the necessary files from the Debian package to use with your source-installed Tomcat.

Related Solutions

Tomcat service start issue

If any server/service has issues, you should always be going straight to the logs.

$:\Tomcat4.1\logs\stdout.log
$:\Tomcat4.1\logs\stderr.log

Windows – Tomcat 7.0.22 Windows service breaks with JRE update

We have observed this with a long-running (but not Tomcat) Java app that runs as a Windows service. 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.

From hints of other reports of this, it seems like the Java update process moves/renames files as part of upgrading to the new version. There might be one or two renames left to do when the install finishes, and those renames are supposed to happen after a reboot. 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.

One symptom of this is to open a command window and type "java -version". 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.

We have found two workarounds: (1) reinstall the app; (2) reinstall Java. (1) usually works for us because we have an installer for the app which will also install a clean version of Java if required. 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). In this case we fall back to (2).

Neither workaround is very nice. It's a shame that the automated JDK update facility provided by Java breaks our application.

Have you made any progress with this since your original posting?

Best Answer

Related Solutions

Tomcat service start issue

Windows – Tomcat 7.0.22 Windows service breaks with JRE update

Related Topic