[zope2-tracker] [Bug 143593] Re: ConflictErrors cause "Shouldn't load state for?"

Hanno Schlichting hanno at hannosch.eu
Sat Apr 3 13:11:51 EDT 2010


I only marked this as "incomplete" as it lacks any information that
could be used to track down the problem. All cases of the "Shouldn't
load state for ..." message I've seen were caused by application code.
Like storing persistent objects in module scope variables, on the
request or any other inappropriate places. Or sometimes by accessing
persistent objects after the db connection was indeed closed, like
sometimes in EndRequestEvent handlers or those request._held hooks.

-- 
ConflictErrors cause "Shouldn't load state for?"
https://bugs.launchpad.net/bugs/143593
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.


More information about the zope2-tracker mailing list