set JAVA_OPTS=%JAVA_OPTS% -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file="%CATALINA_BASE%\conf\logging.properties"
Originally posted by James Hodgkiss:
I also have some servlets hosted on another server. I also asked that guy to change the headless config prooperty. Here is his response:
> I do not think we will be able to set this property due to the possible load it may cause. You may need to move to a VDS or dedicated server if you need to alter Tomcat in this way.
Are his concerns valid??
we have a cron job that runs the script below once a day, with parameter
"stop", then a short pause, then again with parameter "start":
This is a shell script called: /usr/share/tomcat4/bin/james.sh
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#!/bin/sh
# set the environment
CATALINA_BASE=/home/mydomain.com/www/tomcat
CATALINA_HOME=/usr/share/tomcat4
JAVA_HOME=/usr/lib/j2sdk1.4-sun
JAVA_OPTS="-server -Xms20m -Xmx50m -Djava.awt.headless=true"
export CATALINA_BASE CATALINA_HOME JAVA_OPTS JAVA_HOME
exec /bin/su -s /bin/sh tomcat4 "$CATALINA_HOME"/bin/catalina.sh "$@"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The catalina.sh script is quite a long one that comes with the tomcat4
package and is the standard stop/start script for Tomcat. It is
controlled via environment variables such as those set above.
Basically what this wrapper is doing it giving you your own JVM and
config, limiting the memory usage, and running the JVM as a tomcat4
user. This is so you don't get security problems if several users want
to run Tomcat on the same machine.
Consider Paul's rocket mass heater. |