• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Detecting crash and autorestart
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Detecting crash and autorestart


  • Subject: Re: Detecting crash and autorestart
  • From: DevReseune <email@hidden>
  • Date: Thu, 14 Aug 2003 18:34:03 +0200

Thanks again. I saw the framework from Wonder that you mentioned, and it's what I need.


Le jeudi, 14 ao{ 2003, ` 17:38 Europe/Paris, Chuck Hill a icrit :

I'm not clear on how (or even if) wotaskd could detect deadlock. The app
is still accepting requests from wotaskd. It still responds to the heart
beat requests. The problem (from wotaskd's point of view) is that the app
does not send back a response in time (well, never). wotaskd does not wait
forever :-) to check this out, it waits a while and then gives up and moves
on. It has no way of knowing if something is deadlocked or if your code is
just really slow and doing a large job.


Perhaps there is a way, but the frameworks that I mentioned seem the right
way to go. The app knows best what is happening internally and can best
decide when to kill itself.


WO is not qualified on JDK 1.4.x.  There is a possibility that this is
constributing to your problem.


Chuck


At 01:05 PM 14/08/2003 +0200, DevReseune wrote:
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




--

Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
_______________________________________________
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.

  • Follow-Ups:
    • Re: Detecting crash and autorestart
      • From: John Boynton <email@hidden>
References: 
 >Re: Detecting crash and autorestart (From: Chuck Hill <email@hidden>)

  • Prev by Date: Xcode and WebObjects 5.2
  • Next by Date: Re: Detecting crash and autorestart
  • Previous by thread: Re: Detecting crash and autorestart
  • Next by thread: Re: Detecting crash and autorestart
  • Index(es):
    • Date
    • Thread