On Jan 22, 2009, at 12:54 PM, Anjo Krank wrote:
Am 22.01.2009 um 21:43 schrieb Mike Schrag:
Had the same problem some years ago. Here's the solution:
You need to add -WODirectConnectEnabled NO to the launch
arguments in Monitor. When this is enabled, it disables Refuse
New Sessions.
Chuck
For the record, and just to keep things exciting, Anjo just ran
into some load balancing problems that were SOLVED by turning
WODirectConnectEnabled on :)
Because that is the way it works. In WOApp.refuseNewSessions(true)
you get an exception if the app is in development mode (DC enabled).
So it looks like ... drumroll ... Chuck is wrong. I'd never have
thought I'd see this day :)
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".
I turned if off because the app won't schedule otherwise (which I
think is a bug).
I agree.
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
