On 26-Sep-08, at 12:03 AM, Thomas wrote:
The server has a low CPU load and low request rate, so it's not the
server. I believe that some requests are causing a deadlock in their
worker thread, and these build up until the max descriptors limit is
reached.
Best you can do is getting a thread dump and check what the hanging
threads where doing and fix that. So limiting the number of worker
threads will still help as you will notice it earlier when an
application hangs.
Easiest way:
Find the hanging instance process id with:
ps -auxwww | grep ApplicationLogfileName-1
Send a QUIT signal:
kill -QUIT <pid>
Find the thread dump in the webobjects.log file if you specified:
#!/bin/sh
$@ 1>>/var/log/webobjects.log 2>&1 &
in:
/System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/
Resources/SpawnOfWotaskd.sh
That will give you more information than logging the requests ...
cug
--
Real World WebObjects Bootcamp at the Big Nerd Ranch:
http://www.bignerdranch.com/classes/real-world_webobjects.shtml
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
