kepes.krisztian wrote at 2004-10-4 09:24 +0200:
... 2004-07-20T16:32:35 ERROR(200) ZODB Couldn't load state for 0000000000000e80 Traceback (most recent call last): File "c:\zope\lib\python\ZODB\Connection.py", line 562, in setstate self._set_ghost_state(obj, p) File "c:\zope\lib\python\ZODB\Connection.py", line 607, in _set_ghost_state setstate(state) File "c:\zope\lib\python\Products\Transience\Transience.py", line 881, in __setstate__ new_slices = getTimeslices( AttributeError: _period
I know this problem when I have an inconsistency between our own "Transience" implementation or the stock "Transience" implementation on which it builds. Almost surely, this is not the reason for you. But maybe, you, too, have either a code or code/data inconsistency? Did you make a clean install of "Transience"? Do your session data lives in a RAM storage (default) or in a FileStorage?
... When I try to change server to 2.7.3.b, it is drop another errors:
2004-10-01T17:30:30 ERROR(200) ZODB Couldn't load state for 0x0e44 Traceback (most recent call last): File "c:\zope\lib\python\ZODB\Connection.py", line 600, in setstate self._set_ghost_state(obj, p) File "c:\zope\lib\python\ZODB\Connection.py", line 645, in _set_ghost_state setstate(state) File "c:\zope\lib\python\Products\Transience\Transience.py", line 977, in __setstate__ oldlength = state['_length'] KeyError: '_length'
Apparently, your session data lives in a long living storage (not RAMStorage) and the session pickles there lack some information which is not relevant. Shut your Zope down and discard all existing session data. -- Dieter