The command line arguments for starting Resin 4.0.x only applied to the
watchdog and NOT the actual resin process itself. JVM command line
arguments are specified in resin.xml. For example, in the command above,
$JAVA_MX and $JAVA_MS applies to the watchdog only. I wouldn't increase the
default
Ah excellent catch. I just copied those from my 3.0 startup script and
what you said makes complete sense. I will revisit each parameter
carefully.
Thanks,
Aaron
On 3/22/2010 10:20 AM, Bill Au wrote:
The command line arguments for starting Resin 4.0.x only applied to
the watchdog and NOT
Resin version: resin-pro-3.1.9
I am trying to convert my resin-pro-3.0.23 startup scripts and
resin.conf file to work with resin-pro-3.1.9. It's close, but there is
a small error. I am trying to build a start script similar to:
$RESIN_HOME/bin/httpd.sh -verbose \
-J-server \
-J-Xmx$JAVA_MX \
I think what you want to do is add
class-loader
library-loader path=/opt/server/java/
/class-loader
To your resin.xml. At least, that's how I do it in resin-4.0.x
In 4, you can also add all those Java args in the resin.xml file (I think you
can in 3.1, too, but
It's working now. For completeness and to help others moving from 3.0.x
to 3.1.x or 4.0.x you should change your startup script from this style
(which relies on a wrapper.pl):
$RESIN_HOME/bin/httpd.sh -verbose \
-J-server \
-J-Xmx$JAVA_MX \
-J-Xms$JAVA_MS \
-J-verbose:gc \
Discussion for the Resin application server
Subject: Re: [Resin-interest] Classpath Question
It's working now. For completeness and to help others moving from 3.0.x
to 3.1.x or 4.0.x you should change your startup script from this style
(which relies on a wrapper.pl):
$RESIN_HOME/bin/httpd.sh -verbose
