tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <>
Subject Re: svn commit: r1137607 - /tomcat/trunk/bin/
Date Mon, 20 Jun 2011 13:53:39 GMT
On 20.06.2011 15:41, Mladen Turk wrote:
> On 06/20/2011 03:28 PM, Mark Thomas wrote:
>> On 20/06/2011 14:21, Mladen Turk wrote:
>>> Just don't see what was the problem with that option that
>>> would require it to go away. This wasn't discussed on the dev list
>>> so if I weren't tracking the svn commits it would be a big surprise on
>>> the next tomcat release.
>> Look at the patch again. It only removes the option for configtest
> It depends what you have in CATALINA_OPTS.
> If you have -d32/-d64 this won't get picked.
> However still don't get it why it was removed?
> Funny, but I was actually trying to add $CATALINA_OPTS
> to the version command, so we get consistent JVM behavior.

We do have two options, JAVA_OPTS and CATALINA_OPTS. The only difference
between them is, for which of the subcommand they are used.

- JAVA_OPTS for all
- CATALINA_OPTS only for starting (and run and debug)

Why are there 2 option lists?

Because at least for the memory sizing you need to have a split. If you
run production tomcat with say 2GB heap, and add the same flag when
running version or stop, then you will temporrarily try to start another
2GB Java process.

Another example are the jmx listeners. If you add a port via the sun
management system property and add it to the stop or version command as
well, the JVM will not be able to start, so the version or stop command
will fail.

In general all commands except those that start a Tomcat (and thus
deploy webapps etc.) should not use that type of params. They should go
into CATALINA_OPTS. Everything that you can use multiple times in
parallel, even for the helper programs can go in JAVA_OPTS.



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message