• 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: Zombies and Dead WOAs... Part Two..
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Zombies and Dead WOAs... Part Two..


  • Subject: Re: Zombies and Dead WOAs... Part Two..
  • From: Chuck Hill <email@hidden>
  • Date: Fri, 4 Jul 2008 21:29:32 -0700

That very much sounds like what happens if sleep() or terminate() in Session throw an exception.

When this happens next, use jstack to get a thread dump and see if you can see what is stuck.


Chuck


On Jun 27, 2008, at 5:01 AM, Ian Coleman wrote:

I am having the same problem, can't stop instances in monitor. Just started for me last couple days not a whole has changed in the app in those few days, but not sure how long it has been going on so it could be from changes made a week or two ago. i Did see an email in another list i think saying something about WOResponse getting stuck but i don't think that is the issue in my app.





thanks
ian
On Jun 27, 2008, at 12:22 AM, John Lennard wrote:

Okay,
So I will try this again, having been bested by my mail program :-/

I am currently having issues with instances "gumming up" and seemingly deadlocking and I also noticing lots of Zombie Java processes being created after an application restarts.



So my questions are really two fold..



Firstly, is it possible to attach Eclipse as a debugger to a remote running instance in order to see why things are fouling up. I have read Andrew Lindesay's document on using jdb, but I am hoping that there may be a way to debug everything in a little more detail. Worst case, I can pester him since he is in the office next door :-p

The processes that are deadlocking tend to also then not want to be killed by the monitor and need to be dealt with the good old fashioned way and need to be killed with a sig KILL...



Secondly, has anybody else seen or experienced these zombie webobjects processes that appear after monitor/wotaskd restarts. I have already tried the wonder monitor and wotaskd and these dont seem to fix anything.



I am currenly running on WO 5.3.4 and Tigger Server..



Thanks

John


_______________________________________________ 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


_______________________________________________ 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


--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects






_______________________________________________
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


  • Prev by Date: Re: Zombies and Dead WOAs... Part Two..
  • Next by Date: directActionURLForActionNamed produce corrupted hostname
  • Previous by thread: Re: Zombies and Dead WOAs... Part Two..
  • Next by thread: directActionURLForActionNamed produce corrupted hostname
  • Index(es):
    • Date
    • Thread