Hmmmm... maybe the right thing is to bite the bullet and do the upgrade. On Thu, 20 May 2004, Chris McDonough wrote:
In that case, you can probably take these files out of the 2.7 CVS branch and try them in 2.6:
Products/Transience/Transience.py Products/Transience/TransientObject.py Products/Sessions/SessionDataManager.py tempstorage/TemporaryStorage.py
Note that if you do this, and if you *don't* keep your session data in a TemporaryStorage (e.g. within /temp_folder/session_data) and instead have your session data in a persistent storage, it's safest to delete and recreate the "transient object container" object you're using to do so. You will need to do this if you switch back to the older code too.
I fear there may be some (shallow) dependencies on Python 2.2+ in these versions of the modules, so if you're running Python 2.1, you may need to fix them. I can help with this as necessary if you try it first.
There are also pending fixes to:
ZPublisher/Publish.py Zope/App/startup.py
... that have not been checked in anywhere, but effect session access during an error message... I'd suggest for now you just don't try to do that.
- C
On Thu, 2004-05-20 at 15:45, Dennis Allison wrote:
Thanks Chris. I'm a bit worried that moving to 2.7.X may be risky. When last I looked, not all the products we use had been vetted agains 2.7 and Python 2.3. At the current point in time, we cannot afford any downtime.
On Thu, 20 May 2004, Chris McDonough wrote:
I do suggest running Zope 2.7.1 when it comes out to help solve the sessioning issues you're experiencing. If you are in a hurry or you want to help test, you can run the current Zope 2.7 branch from CVS and provide feedback.
- C
On Thu, 2004-05-20 at 13:52, Paul Winkler wrote:
On Thu, May 20, 2004 at 10:44:32AM -0700, Dennis Allison wrote:
Zope 2.6.2b3, Py 2.1.3, Linux
We use session variables everywhere and have a fairly large number of concurrent sessions. Every so often the session variables go away and the whole house of cards collapses becasuse nearly everything depends upon session variables.
I tried a while back to isolate the problem without success. At that time someone suggestedit was a known problem open problem. I've just checked the collector and did not see any open issues there. The frustrating thing is that it is the irreproducable Heissenbug behavior.
Can anyone shed additional light on the issue. Is anyone else observing similar behavior? Or is the problem something due to the way we are using session variables.
Check the zope-dev list archives, session & transience issues have been under discussion a lot in the past few weeks. Chris McDonough and others have been digging into it. I'm just a bystander, but it sounds likely that sessions in the 2.7.1 release will be much better, if not yet flawless.
_______________________________________________ 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 )