Re: Limiting max number of sessions
Re: Limiting max number of sessions
- Subject: Re: Limiting max number of sessions
- From: Chuck Hill <email@hidden>
- Date: Tue, 9 Mar 2004 13:54:48 -0800
Running sufficient instances and lowering session timeout is the best
way to deal with spikes. If you implement what you have outlined then
users will get 'No instance available' error messages during spikes.
That said...
public WOResponse dispatchRequest(WORequest aRequest) {
WOResponse result = super.dispatchRequest(aRequest);
refuseNewSessions(activeSessionsCount() > 100);
return result;
}
Should work.
Chuck
On Mar 9, 2004, at 9:45 AM, Anthony Paras wrote:
If your WO app gets a spike in visitors, it will happily create
sessions
until there is no more memory and then lock up.
Has anyone come up with a technique for preventing this? I guess you
could
either terminate the oldest sessions, or else prevent new sessions, or
else
make newer sessions with smaller and smaller session timeouts as they
grow
in number.
Anyone?
_______________________________________________
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.
_______________________________________________
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.