I've never seen this, so this is just a random idea: Do you have access
to the web server log files (and do you log cookies)? If so, can you
verify that the client browser was sending in the same cookie value to
the server at the point where they got redirected to the login? If the
client didn't send the same cookie values then the server would have no
choice but to assign a new value. If you can verify that the client was
doing the right thing then I imagine that helps to isolate the problem
to the server.
Just an idea...
Mark
-----Original Message-----
From: Jason Dunaway [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 9:33 AM
To: CF-Talk
Subject: What conditions would cause a new jsessionid to be assigned to
a user session?
I know this may be a rather rookie question, but I want as much input as
possible on this so I'm asking it anyways.
We're having problems with users being timed out prematurely, before the
2hr time limit our client has decided upon. Everything has been setup
in CFadministrator correctly, as 95% of the users are able to stay
logged in for the 2hr time frame and have no problems. With the small
percentage of users that are not being able to stay logged, the timeout
is random and the server assigns a NEW jsessionid to them. Of course,
when this happens all of the user info that is stored in session is
lost, therefore they are gracefully kicked out of the site and asked to
log in again.
Anyone have any input as to what can be causing this? Thanks!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Create Web Applications With ColdFusion MX7 & Flex 2.
Build powerful, scalable RIAs. Free Trial
http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJS
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:275152
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
