App stopped running but not auto-recovered
App stopped running but not auto-recovered
- Subject: App stopped running but not auto-recovered
- From: Corin Lawson <email@hidden>
- Date: Thu, 4 Oct 2007 13:39:29 +1000
Hi List,
I'm having difficulties with Auto Recover (in JavaMonitor).
(1) When I add a new instance it is added with Auto Recover turned on
but doesn't automatically start (I've been waiting over 22 mins now).
(2) When I kill an instance (ie `kill -KILL $pid`) JavaMonitor shows
the instance as OFF but doesn't automatically start it again.
(3) When I stop an instance (ie `kill -STOP $pid`) JavaMonitor shows
the instance as OFF and generates the email notification below but
doesn't attempt to start it (apparently).
(4) When I stop and immediately kill and instance (ie `kill -STOP
$pid; kill -KILL $pid`) I get the same response as (2), ie no email.
Finally, I tried all the other signals but they had the same effect
as KILL or no effect (AFAIK).
Is this normal?
Is it possible to kill an instance from the command line and have
JavaMonitor start it?
Cheers,
Corin.
Begin forwarded message:
From: email@hidden
Date: 4 October 2007 1:08:49 PM
To: email@hidden, email@hidden
Subject: App stopped running: BDERS-Dev-10
The application Dev-10 listening on port 2028 on host
bottledomains.net.au stopped running at 2007-10-04 03:08:49 Etc/
GMT. This may be the result of a crash or an intentional shutdown
from outside of wotaskd
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden