Re: Detecting crash and autorestart
Re: Detecting crash and autorestart
- Subject: Re: Detecting crash and autorestart
- From: DevReseune <email@hidden>
- Date: Thu, 14 Aug 2003 13:05:05 +0200
My WO version is 5.1.3 (on linux) with JVM 1.4.1. I wait the next
release of WO to upgrade my system.
So, wotaskd doesn't detect "deadlock"? Bad boy!
Frederic
Le mercredi, 13 ao{ 2003, ` 20:14 Europe/Paris, Chuck Hill a icrit :
Hi,
At 12:19 AM 13/08/2003 +0200, DevReseune wrote:
Hi,
My application crashed sometimes (I don't know why). It was not
terminated, it ran again with too many theads, but it couldn't
response
to request.
That sounds like deadlock, not a crash. Which version of WO? Upgrade
if
possible.
So I want wotaskd restarts a crashed instance,
That is not a crash, that is deadlock.
and I set
the "autorecover" option of my instance in JavaMonitor. I didn't
detect
new crash since I do that, but I'm not sure is because wotaskd detects
crash and do all necessary jobs.
wotaskd detects the JVM terminating and sometimes hung instances.
My question is: can wotaskd kill an instance (on Unix "kill
applicationId")
No.
or am I lucky and no new crash arrives?
Yes.
Indeed, I didn't see any line to kill an instance in WO source code
But, we haven't the sources, naturally! ;-)
WOApplication.application().terminate();
There are some frameworks WOSepuku, wOHarakiri?) in Project Wonder that
will allow an app that is in trouble to terminate.
Chuck
--
Chuck Hill email@hidden
Global Village Consulting Inc.
http://www.global-village.net
Cordialement.
Fridiric Mascaro
email@hidden
http://www.reseune.fr
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.