9.3. Use Jsvc with Tomcat 6


Unlike Tomcat 7, there is no wrapper script available to use when running Jsvc with Tomcat 6. Users can write their own scripts for this purpose using the configuration parameters described in the following table:
Expand
Table 9.2. Jsvc Configuration Variables for Tomcat 6
OptionsDefault ValueDescription
-home/home2/java/j2sdk{version}The Java home directory location. Tomcat 6 requires JDK version 1.6 or later.
-Dcatalina.home/opt/jboss-ews-2.0/tomcat6The Tomcat installation directory.
-usertomcatThe user Tomcat uses.
-Djava.io.tmpdir/var/tmpThe temporary directory used by Tomcat 6.
-pidfile/var/run/jsvc.pidThe file where the process ID (PID) for the running instance of Tomcat is stored.
-Dcatalina.base/opt/jboss-ews-2.0/tomcat6The directory that contains the specific configuration and set up information if multiple servers are using the same installation.
-outfilestdoutThe file where the stdout output of the embedded Java Virtual Machine is redirected.
-errfilestderrThe file where the stderr output of the Java Virtual Machine is redirected.
-stop-Stops Jsvc cleanly. The PID file location set with the -pidfile parameter contains information created when Jsvc starts. This file and its information is used to stop the Jsvc instance.
Parameters that are used after specifying an option (for example, the parameters in the table that begin with -D) are used by the embedded Java Virtual Machine that is started by Jsvc. The following is an example of how such parameters are used:
-Djava.library.path=/opt/jboss-ews-2.0/tomcat6
Similarly, the classpath can be added using -cp. The following example illustrates a sample classpath option that starts org.apache.catalina.startup.Bootstrap:
-cp $JAVA_HOME/lib/tools.jar:$CATALINA_HOME/bin/commons-daemon.jar:$CATALINA_HOME/bin/bootstrap.jar
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red Hat
Back to top