IIRC, leaving a browser open on one of the JavaMonitor pages that
refreshes periodically aggravated this bug.
Chuck
On Mar 29, 2006, at 10:04 AM, Sacha Michel Mallais wrote:
On Mar 28, 2006, at 7:23 PM, Corin Lawson wrote:
Recently I have found that under a increased load there is a large
number of tcp connections in CLOSE_WAIT state. When there is
enough of them the adapter to no longer able to find any app
(including the JavaMonitor) and the whole system grinds to a halt...
I have confirmed that WODeployment 5.2.3 is installed on Mac OSX
10.3.
Please help! How can I get rid of the CLOSE_WAIT states?
The cause is a bug in wotaskd in WO 5.2.2 and 5.2.3. The only real
solution is to upgrade to WO 5.2.4.
If that is not possible, a workaround is to simply kill wotaskd
once a night. It may also be possible to write a script to detect
this condition and kill wotaskd.
sacha
PS. I've added this to Chuck and my mini-WO FAQ at http://
www.global-village.net/gvc.webobjects/faq. If anyone has anything
to add to this FAQ, please let me know -- I can give privileges to
add/modify too...
--
Coming in 2006 - an introduction to web applications using WebObjects
and Xcode http://www.global-village.net/wointro
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 protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
