How can start tomcat server

Usually, the shutdown process goes smoothly and Tomcat JVMs shut down quickly. But, because there are situations when they don't, the above procedure should always suffice. We realize this is not a very convenient way to restart Tomcat; however, if you try to cut corners here, you will likely not always shut down Tomcat and get errors due to the new Tomcat JVM bumping into the existing Tomcat JVM when you go to start it again.

Luckily, for most operating systems, there are scripts that automate this entire procedure, implemented as a "restart" command. The following outlines how to reliably restart Tomcat on Linux. If you installed the RPM package from this book, do:. And, if you installed the JPackage. Be sure to check your logfiles for any startup problems. The following outlines how to reliably restart Tomcat on Solaris. As of this writing, the Blastwave package's init script does not contain any code to reliably restart Tomcat—it does not watch the processes to make sure that they came down all the way, nor does it try to force the processes down if they do not come down on their own.

Read the init script source and you'll see what we mean. So, it is up to the Solaris administrator to ensure by hand that the restart actually occurred. If you have Tomcat running as a Windows Service, you can restart it from the control panel. Either right-click on the service and select Restart from the pop-up menu or, if it exists on your version of Windows, use the Restart button near the upper-right corner of the dialog box see Figure If you have chosen to use the generic way to start Tomcat, there is no easy way to restart Tomcat in Mac OS X and the best solution is to call shutdown.

Then, just as described in the Linux section of this chapter, you would decide how long you will wait for Tomcat to shut down and take the appropriate steps, as outlined above. A simple way to see if Tomcat is running is to check if there is a service listening on TCP port with the netstat command.

This will, of course, only work if you are running Tomcat on the port you specify its default port of , for example and not running any other service on that port. You should see no output, meaning that Tomcat has shut down. Then, you may start it back up again, like this:. After waiting some seconds, check to make sure that Tomcat is running and listening on port again:.

If you have chosen to use the automatic startup and shutdown scripts for Tomcat via Apple's launchd see the section " Automatic Startup on Mac OS X ," later in this chapter, for details about how to set that up , it's very easy to restart Tomcat simply by unloading the service and reloading it into launchd :.

You can restart the Tomcat 6 port by running:. That should reliably restart Tomcat. However, renaming these to your preferred conventions is only temporary, as the.

You are better off getting used to typing catalina. That is false. The servlet specification does not preclude doing this, so it is OK to spawn one or more threads as long as the thread s are well behaved. This is often the rub, since webapp developers often report bugs against Tomcat that turn out to be caused by their own code running in a separate thread.

Skip to main content. Tomcat: The Definitive Guide, 2nd Edition by. Start your free trial. Starting, Stopping, and Restarting Tomcat. Starting Up and Shutting Down. Table Tomcat invocation scripts Script Purpose catalina The main Tomcat script. Example Startup options Option Purpose -config [ server. Environment variables. Starting and stopping: The general case. Starting and stopping on Linux. Starting and stopping on Solaris. Starting and stopping on Windows.

Starting and stopping on Mac OS X. Starting and stopping on FreeBSD. Common Errors. Another server is running on port 80 or Ensure that you don't have Tomcat already started. Restarting Tomcat. The general case. Restarting Tomcat on Linux. Restarting Tomcat on Solaris.

Restarting the Tomcat Windows Service. This script installs and uninstalls Tomcat as a Windows service. This runs catalina stop and shuts down Tomcat. This runs catalina start and starts up Tomcat. This prints out a summary of the command-line options. This enables the use of the catalina. This starts Tomcat in debugging mode. This starts up Tomcat without redirecting the standard output and errors. This outputs Tomcat's version information. This sets the directory for Tomcat temporary files.

This is where you may set any Java command-line options. This allows, for example, running Tomcat as a non privileged user while still being able to use privileged ports. Note that if you use this option and start Tomcat as root, you'll need to disable the org.

SecurityListener check that prevents Tomcat starting when running as root. In particular, the -debug option is useful to debug issues running jsvc. Installation as a service : Tomcat will be installed as a Windows service no matter what setting is selected.

Using the checkbox on the component page sets the service as "auto" startup, so that Tomcat is automatically started when Windows starts. For optimal security, the service should be run as a separate user, with reduced permissions see the Windows Services administration tool and its documentation. The options are separated using either or ; characters. If you need to embed either or ; characters, put them inside single quotes. Not used in exe mode. One of jvm , Java or exe.

The modes are: jvm - start Java in-process. Depends on jvm. Java - same as exe, but automatically uses the default Java executable, i. Class that contains the startup method.

Applies to the jvm and Java modes. List of parameters that will be passed to either StartImage or StartClass. Parameters are separated using either or ; character. See --StartMode for further details. Class that will be used on Stop service signal. List of parameters that will be passed to either StopImage or StopClass.

Defines the service log filename prefix. The log file is created in the LogPath directory with.