Re: refuseNewSessions knocks out app instance
Re: refuseNewSessions knocks out app instance
- Subject: Re: refuseNewSessions knocks out app instance
- From: Chuck Hill <email@hidden>
- Date: Mon, 5 Apr 2004 09:02:06 -0700
I've seen this with direct actions where the instance number and
session ID were stored in cookies. I'd imagine it could also happen
with bookmarked direct actions that indicated the instance number in
the URL.
The fundamental problem is that the woadaptor knows nothing about the
app refusing new sessions. When it detects an instance number it just
blindly forwards the request. In my case I overrode dispatch request
and returned a direct to the requested URL after removing all traces of
the instance number.
Chuck
On Apr 4, 2004, at 5:53 PM, Anthony Paras wrote:
When your app instance is gracefully shutting down, you can sometimes
get
bitten by a problem whereby the log says:
<WOApplication> !!! _initializeSessionInContext: called with
refuseNewSessions set !!!
And then the app hangs. Does anyone have any new information about this
problem?
Someone mentioned a while back that they overrode dispatchRequest to
fix it,
but I'm a little hesitant to do that.
- Tony
_______________________________________________
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.