More Core Session Tracking Woes :-(
Hi, The setup: -Zope 2.2.4 -Core Session Tracking 0.7 -Cookie session ID manager (path=/,lifetime=0) -Internal Session Data Manager (timeout set to 60 minutes) This seems to randomly (but sometimes very frequently) loose session data items :-( I've sprayed lots of log statements around (including in SessionData.invalidate, to ensure I wasn't inadvertently calling it) and so far it appears that the session id cookie is being returned by the browser (so path, lifetime, etc are probably okay) but self.session.getSessionData().get('Type','') is often returning an empty string, even when I know it has been set. This is an intermittent problem though, so it's probably going to be a bitch to track down :-( There's doesn't seem to be any correlation with the 'Can't Load State for x' problem I reported earlier, but I guess it could be the same thing. Anyway, please help, I'm loosing (hair|sleep|etc) over this :-( cheers, Chris
Hi!
The setup: -Zope 2.2.4 -Core Session Tracking 0.7 -Cookie session ID manager (path=/,lifetime=0) -Internal Session Data Manager (timeout set to 60 minutes)
This seems to randomly (but sometimes very frequently) loose session data items :-(
FYI, you are not the only one.. I also experienced that. That's also the reason why I am back to using SQLSession again.. (actually I was too lazy to track it down..) -- mr topf -- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
Christian Scholz wrote:
FYI, you are not the only one.. I also experienced that. That's also the reason why I am back to using SQLSession again..
How hard was that to swap in?
(actually I was too lazy to track it down..)
Well, if it makes any difference, it doesn't _appear_ to happen in Zope 2.3.1b1, but there are other reasons (Catalog, buggy Python Scripts) why we can't currently move our production servers to 2.3.1b1-3... cheers, Chris
Hi!
FYI, you are not the only one.. I also experienced that. That's also the reason why I am back to using SQLSession again..
How hard was that to swap in?
depends. Of course the API is not the same.. So it depends if you've factored out the session stuff in some dtml or python method which you simply have to change. (and if you can factor it out, of course.. I basically just looked one variable up in the session and copied it to REQUEST, so I simply had to change one header file). Also I haven't written a plugin for my Virtual Site Root yet to make use of the Core Session Tracking package so I cannot use it in siterooted environments yet anyway.. cheers, MrT -- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
Well, if it makes any difference, it doesn't _appear_ to happen in Zope 2.3.1b1, but there are other reasons (Catalog, buggy Python Scripts) why we can't currently move our production servers to 2.3.1b1-3...
Hmmm... this sounds like a bug in expiration code. I sent Chris a prerelease CoreSessionTracking 0.8 which has new expiration code. Hopefully I can release soon. I know I've been saying that for a while now... ;-) BTW, what's the problem with the Catalog preventing you from moving to 2.3.1b3?
Chris McDonough wrote:
Hmmm... this sounds like a bug in expiration code. I sent Chris a prerelease CoreSessionTracking 0.8 which has new expiration code. Hopefully I can release soon. I know I've been saying that for a while now... ;-)
I'm checking this out right now :-) Christian, mail me if you want a copy...
BTW, what's the problem with the Catalog preventing you from moving to 2.3.1b3?
Miscall on my part, sorry ;-) The only failing test we had on 2.3.1b3 was caused by a problem with Python Scripts in b2 and b3, Philip Mayers posted a patch to this on the zope list but there's been no word from Evan as to whether it's a sound patch or not. Thanks for all your help, Chris
Chris McDonough wrote:
Hmmm... this sounds like a bug in expiration code. I sent Chris a prerelease CoreSessionTracking 0.8 which has new expiration code. Hopefully I can release soon. I know I've been saying that for a while now... ;-)
Well, the prerelease seems to solve the problem :-) cheers, Chris PS: Chris, any chance you could stick a version.txt in 0.8? I just got myself real confused as to which version I was actually running thanks to a combination of INSTANCE_HOME and the version not showing up on the products page ;-)
PS: Chris, any chance you could stick a version.txt in 0.8? I just got myself real confused as to which version I was actually running thanks to a combination of INSTANCE_HOME and the version not showing up on the products page ;-)
Done, thanks!
Chris Withers wrote:
This is an intermittent problem though, so it's probably going to be a bitch to track down :-( There's doesn't seem to be any correlation with the 'Can't Load State for x' problem I reported earlier, but I guess it could be the same thing.
Hmmm... onStart and onEnd could be really useful to try and track down what's going on here. Did anyone get anywhere in implementing those two? cheers, Chris
This is part of the new (as yet to be released) code that I sent to you earlier. ----- Original Message ----- From: "Chris Withers" <chrisw@nipltd.com> To: <zope-dev@zope.org>; "Chris McDonough" <chrism@digicool.com> Sent: Monday, March 26, 2001 10:20 AM Subject: Re: [Zope-dev] Core Session Tracking: onStart and onEnd?
Chris Withers wrote:
This is an intermittent problem though, so it's probably going to be a
bitch to
track down :-( There's doesn't seem to be any correlation with the 'Can't Load State for x' problem I reported earlier, but I guess it could be the same thing.
Hmmm... onStart and onEnd could be really useful to try and track down what's going on here. Did anyone get anywhere in implementing those two?
cheers,
Chris
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
participants (3)
-
Chris McDonough -
Chris Withers -
cs＠comlounge.net