Re: WO blocking/threading question
Re: WO blocking/threading question
- Subject: Re: WO blocking/threading question
- From: David Teran <email@hidden>
- Date: Mon, 16 Aug 2004 10:52:36 +0200
Thanks for your explanation, Karl,
I'm still a little puzzled about WO servlet deployment. It seems that
the jsp/servlet container is best suited to a multithreaded model for
concurrent request handling, but among other reasons, since EOF is
single threaded, running multiple instances is probably the best
approach to scaling WO apps.
Am I missing something or is it fair to say you're best off sticking
with multiple instances and the old school web server adaptor for
scaling WO apps? It doesn't appear to be possible to have the servlet
adaptor instantiate multiple instances of a web app within the same
vm.
If this is the case when is it appropriate to use SSDD?
Dov? How do you deal with WO/EOF performance using the servlet
adaptor?
AFAIK its true that for each servlet container you have 'only' running
one instance from your app... but who tells you not to deploy one and
the same app with different names ? Maybe this works fine.
But the real problem is still: EOF deadlocks when concurrent request
handling is set to true. In order to fix this EOF should be able to
detect a deadlock and throw somewhere. If anyone has EOF deadlocks,
please send me the stack traces, i would love to see the traces, for
studying.
regards David
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.