Hi Dieter ! Dieter Maurer wrote:
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.
Sorry, but I didn't understand, what you wrote about. I do that: I install zope 2.7.1 in window xp, and I use it. And I install 2.7.x (?) in debian linux (compile), and I use it. Every installer is came from zope.org. I use these products: External Editor, KinterbasdbDA, and my owned product. No one of these products are used by session. So: session. When I log in to server, I put 8 items to session, and I read them in every request. I don't store anything else in session, I use my websessionstore table to exchange datas. This code in 2.6.3 is working good. And it is working good with my localhost (Mozilla, IE, etc). The problem is get when I want to show the page to my boss, and his IE is crashing my zope with these session errors. But I'm the man who not like the non-repeatable errors. If a component or program drop an errors, I never trust in it again. If I get this problem with boss-IE, possible (may be) I get this error with another IE (the program users are many). So how to I trust in Zope 2.7.x ? Yesterday I try to downgrade, but the 2.6.4 have a problem with kinterbasdbda, and I cannot do that.
Almost surely, this is not the reason for you.
Not the reason, or not reasonable for me ? :-) (Yes, these errors are not reasonable for me !)
But maybe, you, too, have either a code or code/data inconsistency?
What do you think when you write this ?
Did you make a clean install of "Transience"?
I use zope's windows installer. In debian I compile with setup. (In debian I don't see this problem, only in my developer machine (win). But if is exists in win, may be exists in debian !).
Do your session data lives in a RAM storage (default) or in a FileStorage?
Yes, I use RAM storage. How to I use file storage ? Please help me: how to I install, or where I found this product ?
... 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.
2..7.3b is a trying. It is drop this error, when I try to find something in the zope man. intf. So not that the main problem.
Shut your Zope down and discard all existing session data.
Ahhh... But it is not too good. Many user working with zope system. If anyone make this error, all user are pushed out, because RAM st. is cleared, so they are must be login again to continue work... Thanx: KK