On 22.07.2010 17:24, David Fisher wrote:
If you look at catalina.sh you will see that stop does not include CATALINA_OPTS:"$_RUNJAVA" $JAVA_OPTS \ -Djava.endorsed.dirs="$JAVA_ENDORSED_DIRS" -classpath "$CLASSPATH" \ -Dcatalina.base="$CATALINA_BASE" \ -Dcatalina.home="$CATALINA_HOME" \ -Djava.io.tmpdir="$CATALINA_TMPDIR" \ org.apache.catalina.startup.Bootstrap "$@" stop Change your catalina.sh to include your CATALINA_OPTS and it ought to work. Looks like a "bug" in Tomcat to me.
Feature, not a bug. There are options that you actually do not want to occur for start and stop, e.g. assume you assign 1GB of heap per commandline parameter. If the same parameter were used for stopping, the shutdown process that lives only a few milliseconds to connect to the shutdown port of Tomcat would also be started with this huge memory size, although it doesn't need it. Another example is using a JMX port. If you use the same flag for the shutdown process, the JVM will not initialize, because it can not bind to the JMX port already in use.
This has been introduced in 6.0.15, see https://issues.apache.org/bugzilla/show_bug.cgi?id=42951 Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
