Re: 5.3 CLOSE_WAIT problem and multi instance change notification
Re: 5.3 CLOSE_WAIT problem and multi instance change notification
- Subject: Re: 5.3 CLOSE_WAIT problem and multi instance change notification
- From: Chuck Hill <email@hidden>
- Date: Tue, 11 Oct 2005 15:57:04 -0700
Hi,
On Oct 11, 2005, at 11:52 AM, Hordur Thordarson wrote:
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 ?
Not normally, but your description of > 100 threads sounds like it is
deadlocked somewhere. Have you tried getting a thread dump?
Also, I was wondering if maybe running multiple instances would
help with this
Even having 40 - 70 threads in one instance says that you want to be
running multiple instances. That many threads indicates that
something is blocking / deadlocking or that that instance is way
overloaded.
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 ?
ERChangeNotificationJMS is a modern version of David Neumann's code.
If I was going to use such a notification system that is the one that
I would choose. So far, I have not found it to be necessary. You
need to plan for object freshness and create new editing contexts /
do refreshing fetches to ensure that you have data as fresh as you
need it. You also need to take care of optimistic locking conflicts,
but those can also happen when using a change notification system.
Chuck
--
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@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden