Re: Apps that don't release unused sessions
Re: Apps that don't release unused sessions
- Subject: Re: Apps that don't release unused sessions
- From: George Domurot <email@hidden>
- Date: Sat, 29 Jan 2005 20:27:10 -0800
By adding this code to your Application object, users that return to
the app get their previous session restored, if it hadn't timed-out yet
- as long as the URL directing the user includes the .woa at the end of
the app name.
I didn't get a stack trace.
I felt this code was the root of the issue since the problem didn't
exist prior to adding the code. And, after removing it, the problem
disappeared.
-George
On Jan 29, 2005, at 5:49 PM, Chuck Hill wrote:
What exactly is the purpose of that piece of code? It seems like
createSession would only be called if it has not already been
determined
that the session could not be restored. Do you have a stack trace?
Why do
you think this code is the cause of your problems?
Chuck
At 12:41 PM 29/01/2005 -0800, George Domurot wrote:
Chuck/Helge/Tim: Thank you for the ideas and pointers. I was able to
pinpoint the issue down to a bit of code I added to restore returning
visitor's sessions. I picked it up from someone's earlier
posting/notes.
Here's the code from the Application class:
public WOSession createSessionForRequest(WORequest aRequest) {
WOSession aSession = null;
WOContext aContext = new WOContext(aRequest);
if (aContext!=null){
String sessionID =
aRequest.cookieValueForKey(WORequest.SessionIDKey);
String instance = aRequest.cookieValueForKey(WORequest.InstanceKey);
if(!XOEO.Empty(sessionID))
aSession = restoreSessionWithID(sessionID, aContext);
}
if(aSession == null)
return super.createSessionForRequest(aRequest);
return aSession;
}
Any ideas why this would cause the problem? Also, looking at the code
a bit
more, the line about the instance number doesn't seem relevant to the
method.
Much thanks,
George
On Jan 27, 2005, at 5:57 PM, George Domurot wrote:
We have an app that doesn't want to release inactive sessions (usually
just
1). This becomes a problem during scheduled graceful cycling.
Has anyone seen this occur? Any ideas about resolution?
There are other apps running under the same deployment scenario for
more
than a year, all smooth.
Any input is appreciated.
Thanks,
George
--
George Domurot
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
george@boxofficet
ickets.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
village
.net
This email sent to email@hidden<<<<
--
Chuck Hill email@hidden
Global Village Consulting Inc.
http://www.global-village.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden