5.3 CLOSE_WAIT problem and multi instance change notification
5.3 CLOSE_WAIT problem and multi instance change notification
- Subject: 5.3 CLOSE_WAIT problem and multi instance change notification
- From: Hordur Thordarson <email@hidden>
- Date: Tue, 11 Oct 2005 18:52:09 +0000
Hi all,
I have a client who is running an app of mine on OSX Server 10.4 with
WebObjects 5.3, and recently we've been having significant problems
with the app, probably as the load on the app has been increasing.
Currently there is just 1 instance of the application running. It will
run fine for a while after being restarted, but then the app will go
into a state where according to top it has > 100 threads as opposed to
around 40-70 normally, and it will become unresponsive. Doing a
netstat at this point in time shows a lot of connections in a
CLOSE_WAIT state and the only way out is to kill the instance and
restart the WebObjects service.
Is anyone seeing anything like this with OSX Server 10.4 and WO 5.3 ?
Also, I was wondering if maybe running multiple instances would help
with this and wanted to ask what people here are using for
multi-instance db change notification. I've read about Project
Wonder's ERChangeNotificationJMS and there is some old code from David
Neumann of Apple floating around but that's all I've been able to find.
Are you guys using ERChangeNotificationJMS or are you using homegrown
stuff for multi instance sync ?
Thanks,
Hörður Þ.
Lausn hugbúnaður ehf
Tel. +354-534-5005 / +354-699-1068
Web: http://www.lausn.is
_______________________________________________
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