CATALINA_OPTS vs JAVA_OPTS - What is the difference?

Question

I was trying to find out the difference between Apache Tomcat variables - CATALINA_OPTS and JAVA_OPTS in SO and surprised to see that there is no question/answer posted here yet. So I thought of sharing it here (with answer) after finding out the difference. Check the answer/difference below.

NOTE: At the time of this posting, we're running Apache Tomcat v6.0.10 with JDK 6u32 on CentOS5 64-bit arch.

Solution

There are two environment variables - CATALINA_OPTS and JAVA_OPTS - which are both used in the catalina.sh startup and shutdown script for Tomcat. They are described in comments within that file as:

[JAVA_OPTS]: (optional) Java runtime options used when the "start", "stop" or "run" command is executed

and

[CATALINA_OPTS]: (optional) Java runtime options used when the "start" or "run" command is executed

So why are there two different variables? And what's the difference?

Firstly, anything specified in EITHER variable is passed, identically, to the command that starts up Tomcat - the "start" or "run" command - but only values set in JAVA_OPTS are passed to the "stop" command. That probably doesn't make any difference to how Tomcat runs in practise as it only effects the end of a run, not the start.

The second difference is more subtle. Other applications may also use JAVA_OPTS, but only Tomcat will use CATALINA_OPTS. So if you're setting environment variables for use only by Tomcat, you'll be best advised to use CATALINA_OPTS, whereas if you're setting environment variables to be used by other java applications as well, such as by JBoss, you should put your settings in JAVA_OPTS.

Source: CATALINA_OPTS v JAVA_OPTS - What is the difference?

Comments

[Joao Figueiredo]

It's also useful to think of them as "do I need something for tomcat startup" or "do I need something for every JVM". Let's say we are trying to setup JMX monitoring on a distributed environment and we're behind a firewall - we'll need two RMI ports thus to set up Djava.rmi.server as a startup arg. Would we do this as a JAVA_OPT a shutdown fires a new JVM which tries to listen on JMX ports, can't grab it as tomcat already has it listening and the JVM will stop with an error about it being already in use - not what we want is it ?

[csd]

Another important difference: daemon.sh erases JAVA_OPTS. So if you're running Tomcat with jsvc and you need to pass options to the Java runtime, be sure to set them in CATALINA_OPTS instead.