[ZODB-Dev] Couldn't load state for xxx after using undo feature

[Anthony Gerrard]

Hi we started receiving the errors below after we used the zope 2 undo tab
to undo an accidental delete of an item in Plone.  We have 2 Zope instances
and the error only occurred in one (many times until I restarted the
server).  I'm wondering if this is a known relstorage bug?

yours

Anthony

2014-06-17T16:19:41 ERROR ZODB.Connection Couldn't load state for 0xed95a1
Traceback (most recent call last):
  File
"/home/zopecms/home/eggs/ZODB3-3.10.5-py2.7-linux-i686.egg/ZODB/Connection.py",
line 860, in setstate
    self._setstate(obj)
  File
"/home/zopecms/home/eggs/ZODB3-3.10.5-py2.7-linux-i686.egg/ZODB/Connection.py",
line 901, in _setstate
    p, serial = self._storage.load(obj._p_oid, '')
  File
"/home/zopecms/home/eggs/RelStorage-1.5.1-py2.7.egg/relstorage/storage.py",
line 457, in load
    state, tid_int = cache.load(cursor, oid_int)
  File
"/home/zopecms/home/eggs/RelStorage-1.5.1-py2.7.egg/relstorage/cache.py",
line 234, in load
    self._check_tid_after_load(oid_int, actual_tid_int, tid_int)
  File
"/home/zopecms/home/eggs/RelStorage-1.5.1-py2.7.egg/relstorage/cache.py",
line 187, in _check_tid_after_load
    'thread_ident': thread.get_ident(),
AssertionError: Detected an inconsistency between the RelStorage cache and
the database while loading an object using the delta_after0 dict.  Please
verify the database is configured for ACID compliance and that all clients
are using the same commit lock.  (oid_int=15570337,
expect_tid_int=263344272409910101L, actual_tid_int=263344508671329280L,
current_tid=263344510277377826L, cp0=263342914987325781L,
cp1=263337834610124202L, len(delta_after0)=6576, len(delta_after1)=10003,
pid=29051, thread_ident=-1223988336)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.zope.org/pipermail/zodb-dev/attachments/20140618/9532348b/attachment.html>