setSessionVariable is a python script that hides the session persistence mechanism but does very little else. It may interecept and re-raise exceptions -- I guess what you are saying is that it interferes with the normal processing that generates the warning message. OPK, easily fixed. On Fri, 18 Feb 2005, Chris McDonough wrote:
No, from the traceback it looks like it comes out of setSessionVariable.py which appears to be a Python Script in another product or within your application directly.
- C
On Fri, 2005-02-18 at 14:52 -0800, Dennis Allison wrote:
Thanks Chris -- looks like the raise was left in the released 2.7.3! I've not yet checked the code, but that certainly is the behavior.
On Fri, 18 Feb 2005, Chris McDonough wrote:
Nope, it's expected behavior for any application that writes to ZODB. Reraising it as an assertion error is the bug (Zope retries requests that encounter conflict errors unless you catch them).
On Fri, 2005-02-18 at 13:56 -0800, Dennis Allison wrote:
We are seeing occasional read conflicts in Transcience.
Traceback (innermost last): [...]] Module Products.PythonScripts.PythonScript, line 323, in _exec Module None, line 6, in setSessionVariable - <PythonScript at /setSessionVariable used for /questionbanks/questionbank_edit/queries> - Line 6 AssertionError: Assignment to "currentQuestionBank" failed database read conflict error (oid 0x1205, class Products.Transience.TransientObject.TransientObject)
Zope 2.7.3 Pythn 2.3
Transcience apparently throws an exception rather than serialize. Is that a bug?
Is this a bug?
_______________________________________________ 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 )