On Jan 22, 2009, at 2:24 PM, Anjo Krank wrote:
Am 22.01.2009 um 22:34 schrieb Chuck Hill:
You need to add -WODirectConnectEnabled NO to the launch
arguments in Monitor. When this is enabled, it disables Refuse
New Sessions.
Sorry, I misread - this en-/disabled thing wasn't really clearly
phrased for my poor language skills :)
I will concede that point. ;-)
No so fast Mr. Krank. I think we are saying the same thing: if you
want to be able to Refuse New Sessions you need to _disable_ Direct
Connect. I am not sure what Mike is talking about, "Anjo just ran
into some load balancing problems that were SOLVED by turning
WODirectConnectEnabled on".
The app sometimes was marked as dead, the problem went away when I
enabled DC. One could reproduce it by reloading a few times, then
you would be transfered to another instance, but after 30 secs (dead
interval from monitor) it would work again. Sometimes.
And it wasn't a mem/refusal problem AFAICS. Also, it looks like it
happens more often in https than in http (??)
Still investigating...
This sounds familiar. I have never tracked it down or played with
enabling DC.
Chuck
--
Chuck Hill Senior Consultant / VP Development
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-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
