When we try to stop the resin-4.0.5 processes using:
$JAVA_HOME/bin/java \
-server \
-Djava.util.logging.manager=com.caucho.log.LogManagerImpl \
-Djava.security.egd=/dev/urandom \
-Dhost=${SERVER} \
-Dresin.home=${RESIN_HOME} \
-jar ${RESIN_HOME}/lib/resin.jar \
-conf
Hi Aaron,
This is the correct behavior. In 4.0.x, we changed the watchdog to be a
long-lived process. If you'd like to shut it down, along with all
running resin instances, use the shutdown command. We're in the
process of updating the documentation this week to reflect the change.
Thanks,
Rick Mann wrote:
I'm seeing that same behavior.
To shutdown the watchdog, use shutdown. start/stop only starts and
stops the Resin instance.
-- Scott
On Mar 30, 2010, at 09:01:23, Aaron Freeman wrote:
When we try to stop the resin-4.0.5 processes using:
$JAVA_HOME/bin/java \
Perfect, thanks!
Aaron
On 3/30/2010 1:49 PM, Emil Ong wrote:
Hi Aaron,
This is the correct behavior. In 4.0.x, we changed the watchdog to be a
long-lived process. If you'd like to shut it down, along with all
running resin instances, use the shutdown command. We're in the
process of
On Tue, Mar 30, 2010 at 11:52:15AM -0700, Rick Mann wrote:
Ah! Thanks. So, does that mean it's safe to leave the watchdog running, and
just issue a start again? I seem to recall Resin getting mad that someone
already had the port when I did that.
That's correct: you can just leave the
Thanks!
On Mar 30, 2010, at 15:25:47, Emil Ong wrote:
On Tue, Mar 30, 2010 at 11:52:15AM -0700, Rick Mann wrote:
Ah! Thanks. So, does that mean it's safe to leave the watchdog running, and
just issue a start again? I seem to recall Resin getting mad that someone
already had the port when I
