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 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 32m max heap size of the watchdog since
it does need much memory.
Bill
On Fri, Mar 19, 2010 at 5:53 PM, Aaron Freeman
<aaron.free...@layerz.com <mailto:aaron.free...@layerz.com>> wrote:
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 <http://wrapper.pl>):
$RESIN_HOME/bin/httpd.sh -verbose \
-J-server \
-J-Xmx$JAVA_MX \
-J-Xms$JAVA_MS \
-J-verbose:gc \
-J-XX:MaxGCPauseMillis=5000 \
-J-XX:GCTimeRatio=19 \
-J-XX:+PrintGCTimeStamps \
-J-Djava.security.egd=/dev/urandom \
-J-cp=/opt/server/java/test.jar \
-server-root $SERVER_ROOT \
-Dresin.home=/opt/resin-pro-3.1.9 \
-conf /opt/server/conf/resin.xml \
$1
To something like this:
$JAVA_HOME/bin/java \
-server \
-Xmx$JAVA_MX \
-Xms$JAVA_MS \
-Djava.util.logging.manager=com.caucho.log.LogManagerImpl \
-Djava.security.egd=/dev/urandom \
-Dresin.home=${RESIN_HOME} \
-jar ${RESIN_HOME}/lib/resin.jar \
-conf ${SERVER_ROOT}/conf/resin.xml \
$*
And by the way that magically fixed my resin:type problem as well.
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
