[Zope] SESSION Errors

[Dennis Allison]

 I'd like to stay with standard release stuff if I can.  That sorta means
 fixing the current product.

On Thu, 19 Feb 2004, David Hassalevris wrote:

> FWIW,
> I used HappySession a few years ago and it worked well for me.  But then, it
> was never run on a busy server.  Still, its very similar to Zope Session and
> if all else fails it may be worth a look.
> I am not sure if HappySession is still supported or if It will run on Zope
> 2.7.  I run it on Zope 2.6x.  Also, if anyone knows of problems w/it I would
> be interested to hear.
> David
> 
> ----- Original Message ----- 
> From: "Dennis Allison" <allison at sumeru.stanford.EDU>
> To: "Chris McDonough" <chrism at plope.com>
> Cc: <zope at zope.org>
> Sent: Thursday, February 19, 2004 1:30 PM
> Subject: Re: [Zope] SESSION Errors
> 
> 
> > Chris--
> > I need to squash this bug.  Any thoughts as to were to begin.  Have you
> > tried to locate the error?
> > -d
> >
> > On Thu, 19 Feb 2004, Chris McDonough wrote:
> >
> > > Yes, this bug is in every version of Zope including the most recent.
> > > Yes, it's bad.  Yes, it should be fixed.  I wish I had a fix for it.
> > >
> > > - C
> > >
> > >
> > > On Thu, 2004-02-19 at 12:35, Dennis Allison wrote:
> > > > Accessing session variables fails occasionally--perhaps once every
> 10000
> > > > references or so!  (See collector issue #848 where I just added a
> > > > comment.)
> > > >
> > > > Presumably this is a read conflict in temporary_folder.  The access to
> the
> > > > variable uses a python script--
> > > >
> > > > request=container.REQUEST
> > > > try:
> > > >     session=request['SESSION']
> > > >     return session[varname]
> > > > except KeyError:
> > > >     container.oopsSession( varname )
> > > >     raise
> > > >
> > > > oopsSession() is a debug routine which reports that it cannot find
> > > > REQUEST.
> > > >
> > > > This is Zope 2.6.2b3 and Python 2.1.3.  This version of Zope is
> patched to
> > > > NOT use the (flawed) LowConflictConnection for temporary storage.
> > > >
> > > > This is a critical bug for us and is becoming more so as our usage
> grows.
> > > > It's a showstopper for our users as we are entirely session based!
> > > >
> > > > It's fairly likely that some internal data structure gets corrupted.
> We
> > > > tend to fetch session variables in clusters, and when one fails all
> > > > subsequent ones fail.  Sad to say, the failure kills the user's
> session
> > > > and releases a burst of emotional energy )-:
> > > >
> > > > Any suggestions for a fix or workaround?   This particular bug has
> been
> > > > seen in 2.7.4 so upgrading is not going to fix things.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Zope maillist  -  Zope at zope.org
> > > > http://mail.zope.org/mailman/listinfo/zope
> > > > **   No cross posts or HTML encoding!  **
> > > > (Related lists -
> > > >  http://mail.zope.org/mailman/listinfo/zope-announce
> > > >  http://mail.zope.org/mailman/listinfo/zope-dev )
> > >
> > >
> > > _______________________________________________
> > > Zope maillist  -  Zope at zope.org
> > > http://mail.zope.org/mailman/listinfo/zope
> > > **   No cross posts or HTML encoding!  **
> > > (Related lists -
> > >  http://mail.zope.org/mailman/listinfo/zope-announce
> > >  http://mail.zope.org/mailman/listinfo/zope-dev )
> > >
> >
> >
> > _______________________________________________
> > Zope maillist  -  Zope at zope.org
> > http://mail.zope.org/mailman/listinfo/zope
> > **   No cross posts or HTML encoding!  **
> > (Related lists -
> >  http://mail.zope.org/mailman/listinfo/zope-announce
> >  http://mail.zope.org/mailman/listinfo/zope-dev )
>