Just been digging some more on this issue and found:
In every case I get this error, the tid's are equal, which suggests your
notes about the <= potentially being bad were correct ;-)
I'm low on fu here, so what's the problem with the two tid's being the
same and do you have any idea why this could be occuring in production
code on Zope 2.9.x?
Chris Withers wrote:
Anyone else seen this?
(864) CW: error in notifyConnected (('x', y))
Traceback (most recent call last):
File "C:\Zope\2.9.2\lib\python\ZEO\zrpc\client.py", line 506, in
File "C:\Zope\2.9.2\lib\python\ZEO\ClientStorage.py", line 521, in
File "C:\Zope\2.9.2\lib\python\ZEO\ClientStorage.py", line 589, in
File "C:\Zope\2.9.2\lib\python\ZEO\ClientStorage.py", line 1114, in
File "C:\Zope\2.9.2\lib\python\ZEO\cache.py", line 151, in setLastTid
File "C:\Zope\2.9.2\lib\python\ZEO\cache.py", line 1060, in settid
raise ValueError("new last tid (%s) must be greater than "
ValueError: new last tid (244611896114584132) must be greater than
previous one (244611896114584132)
First time I've seen it, been running this instance on Zope 2.9.2 for
about a month so far with no problems. But, never got this before ever
with Zope 2.7.x...
Simplistix - Content Management, Zope & Python Consulting
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org