A slight correction for any of you trying to reproduce this at home :-)
I only pretended to change over to filestorage (dream, nightmare, who
knows), in reality, I was still using tempstorage.
Steve
The same thing happened yesterday and re-starting Zope seemed to get
things working again.
Good morning.
I just got in and checked on my customer's system. In the past 22 1/2
hours they've had 15000 page hits and last night at about 9:30, ONE
person got a KeyError. Actually, this same person got twenty KeyErrors
over a period of about 45 seconds. I'm downloading their log files
suggestion on how we should be setting up the
user's session. For now, however, I think I'll just add the
please-don't-cache-me header stuff to the RESPONSE.
Steve Jibson wrote:
Good morning.
I just got in and checked on my customer's system. In the past 22 1/2
hours they've had 15000 page hits
this down and/or test updates.
Steve
Chris McDonough wrote:
On Sat, 2004-05-15 at 23:55, Steve Jibson wrote:
quite yet been vetted (see earlier posts in this thread regarding
Publish.py). This should work itself out over the next week or so I
suspect.
Relatively speaking, this is only a minor concern
Chris McDonough wrote:
On Mon, 2004-05-17 at 13:06, Steve Jibson wrote:
I'm sure 'accountType' should have been in the session. Immediately
after a user logs in we populate his session with a bunch of stuff
(including accountType).
What happens when the session expires and he's still logged
Chris,
Okay, correct me if I'm wrong. This means the big ugly SESSION problem
his completely fixed. If so, you are my new best friend! (whether you
like it or not).
Anyway, I'll put your updates (TemporaryStorage.py and Transience.py)
on a couple of my customer's systems (that have been
Chris McDonough wrote:
On Sat, 2004-05-15 at 23:11, Steve Jibson wrote:
Chris,
Okay, correct me if I'm wrong. This means the big ugly SESSION problem
his completely fixed. If so, you are my new best friend! (whether you
like it or not).
Well, I'm afraid I will need to correct you
Chris,
I'm not sure if you'd even planned to, but have you looked over this
replacement Transience.py? Do you have an opinion on the
re-implementation? I plan on looking over it myself, but even if I like
it, I'd sleep better while it runs on my customer's servers if I knew it
had your
We're always happy about another beta release, but do you think you guys
will have a chance to look into the reported session (thread safety?)
errors before beta 3? I posted and sent some failing test results to
Chris a couple of weeks ago.
Thanks,
Steve
Brian Lloyd wrote:
I'd like to plan to
We have been using Zope 2.7.0-beta2 and we have been having a bit of
trouble with SESSION loosing data when we have more than one user on the
system. These problems usually show up as KeyErrors when a particular
data element in SESSION cannot be found. If I set the zserver threads
to 1 in
to be
able to track this down, but I can't make the test fail under Red Hat
7.3.
On Fri, 2003-10-17 at 15:56, Steve Jibson wrote:
We have been using Zope 2.7.0-beta2 and we have been having a bit of
trouble with SESSION loosing data when we have more than one user on the
system. These problems usually
11 matches
Mail list logo
