Re: JM does not see wotaskd-after some time
Re: JM does not see wotaskd-after some time
- Subject: Re: JM does not see wotaskd-after some time
- From: Chuck Hill <email@hidden>
- Date: Fri, 5 Mar 2010 11:34:07 -0800
On Mar 5, 2010, at 11:05 AM, Ondřej Čada wrote:
Chuck,
thanks a lot!
On Mar 5, 2010, at 7:22 PM, Chuck Hill wrote:
Then, JavaMonitor stops seeing wotaskd ("Failed to contact
localhost-1085").
Simply put: that message lies. What it really means is "wotaskd
timed out trying to communicate with one of the instances"
Uh, this makes quite a difference.
There's bound to be something fishy there (for both instances still
perform their WOTimer-launched internal tasks, none of them is
completely dead) -- must be that _somehow_ one instance fails to
communicate with wotaskd whilst at least part of its code still
works as intended... And there's absolutely nothing in the log (but
for the timer task normal reports, which keep get logged regularly).
This would only indicate the the RR loop is hung / stalled / slow. It
may not affect the timer tasks.
Are you dispatching requests concurrently?
Anyway, thanks again, for from here I can start searching for the
cause of the problem -- what made me to feel crazy was the mentioned
lie which I dumbly did believe -- along with the thing with
Wotimer'd internal tasks it fooled me enough so that I did not try
to kill the instance :(
Grep the logs for OutOfMemory, it could be that.
Nope; no exceptions at all.
I'd be pretty glad for any hint; at this moment I do not really
know what to do
I think you have it. :-) Your application has a problem. That
problem is annoying wotaskd.
Confirmed -- I've killed the instance #1, and immediately the
outrageous "Failed to contact" disappeared and all works (incl. the
other instance, which still runs with much more users and much
longer uptime without a glitch).
(Hmmm. I wonder whether some other task might somehow clash with #1
for the port it runs on?!? Well never mind here, this I hope I can
do myself :))
It really sounds like that app is deadlocking, or has a long running
process. You need to get a thread dump from the instance that is not
responding.
Chuck
--
Chuck Hill Senior Consultant / VP Development
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