Hi Someone may be able to help. Whenever I have zope running with a socket (as is the default for ZEO) my Sessions become unstable. This has happened on two different servers (2.7.3 standalone with HTTPS over socket and 2.7.3 ZEO/Client combo) The sessions are fine 4 out of 5 requests, but the information just disappears every now and then (refreshing the browser shows it still to be there sometimes, others it is just gone). My ZEO is set up to have sessions (tempstorage) on the ZEO and all works fine (MOST OF THE TIME :-s) Any ideas as it is most annoying!!! Ta
On Mon, 06 Jun 2005 18:02:01 +1000, Drew Nichols wrote:
The sessions are fine 4 out of 5 requests, but the information just disappears every now and then (refreshing the browser shows it still to be there sometimes, others it is just gone).
I've seen this behaviour - sessions switching between older and newer information on different requests - come from the usual persistence bug, ie. I've changed the contents of a list or dictionary referenced from the session, but not told the session anything has changed. Thanks, Malcolm. -- [] j a m k i t web solutions for charities malcolm cleaton T: 020 7549 0520 F: 020 7490 1152 M: 07986 563852 W: www.jamkit.com
There are no known bugs in Zope itself after Zope 2.7.3 consistent with what I *think* your observations are. There can be issues caused by not repersisting mutable data, as Malcom described. But that said, I'm not sure I understand what you mean when you say: - "I have my zope running with a socket (as is the default for ZEO)" Do you mean a UNIX domain socket? Or a TCP socket? What process is listening on the socket? - "2.7.3 standalone with HTTPS over socket and 2.7.3 ZEO/client combo" What is standing alone? Can you describe your configuration in more detail? - C On Mon, 2005-06-06 at 18:02 +1000, Drew Nichols wrote:
Hi Someone may be able to help.
Whenever I have zope running with a socket (as is the default for ZEO) my Sessions become unstable.
This has happened on two different servers (2.7.3 standalone with HTTPS over socket and 2.7.3 ZEO/Client combo)
The sessions are fine 4 out of 5 requests, but the information just disappears every now and then (refreshing the browser shows it still to be there sometimes, others it is just gone).
My ZEO is set up to have sessions (tempstorage) on the ZEO and all works fine (MOST OF THE TIME :-s)
Any ideas as it is most annoying!!!
Ta
_______________________________________________ Zope maillist - Zope@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 )
Drew Nichols wrote at 2005-6-6 18:02 +1000:
Whenever I have zope running with a socket (as is the default for ZEO) my Sessions become unstable.
Unbelievable because: 1. Zope is always running with sockets (at least the HTTP socket) 2. We use ZEO and sessions without problems.
... The sessions are fine 4 out of 5 requests, but the information just disappears every now and then (refreshing the browser shows it still to be there sometimes, others it is just gone).
Looks like your sessions contain non elementary non persistent values (such as lists or dictionaries). In this case, you *MUST* modify the session in order to persist changes to these values. Usually, this looks like: complex_value = session[CCCC] # modify complex_value session[CCCC] = complex_value Otherwise, it becomes non-deterministic whether the change is made persistent (and thereby seen by other workers) or remains volatile (and seen only by the worker that made the change). I made a patch for the session machinery to turn this non-deterministic behaviour into a deterministic failure for debugging purposes. I have sent the patch to ChrisM, but he did not understand its purpose and therefore did not add it to the code. @ChrisM: Should we try again? -- Dieter
participants (4)
-
Chris McDonough -
Dieter Maurer -
Drew Nichols -
Malcolm Cleaton