(I tried to send this to zodb-dev@zope.org but got a relay error from ns2.zope.com :-S) Hi All, One of the users on one of my projects saw this error under high load: Module Products.QueueCatalog.QueueCatalog, line 458, in reindexObject Module Products.QueueCatalog.QueueCatalog, line 341, in catalog_object Module Products.QueueCatalog.QueueCatalog, line 284, in _update Module ZODB.Connection, line 732, in setstate Module ZODB.Connection, line 765, in _setstate Module ZODB.Connection, line 791, in _load_before_or_conflict Module ZODB.Connection, line 814, in _setstate_noncurrent AssertionError This is on Zope 2.9.4. Any ideas? cheers, Chris
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Withers wrote:
(I tried to send this to zodb-dev@zope.org but got a relay error from ns2.zope.com :-S)
Hi All,
One of the users on one of my projects saw this error under high load:
Module Products.QueueCatalog.QueueCatalog, line 458, in reindexObject Module Products.QueueCatalog.QueueCatalog, line 341, in catalog_object Module Products.QueueCatalog.QueueCatalog, line 284, in _update Module ZODB.Connection, line 732, in setstate Module ZODB.Connection, line 765, in _setstate Module ZODB.Connection, line 791, in _load_before_or_conflict Module ZODB.Connection, line 814, in _setstate_noncurrent AssertionError
This is on Zope 2.9.4.
Any ideas?
Have you looked at the code? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF9ruJ+gerLs4ltQ4RAi/MAJ4kD3sLixiK5rIZUnO16vbRNNuZjQCfcVNJ T3lDj+D9xiMmwUi6uiLFAyo= =O3Op -----END PGP SIGNATURE-----
Tres Seaver wrote:
Module ZODB.Connection, line 814, in _setstate_noncurrent AssertionError
This is on Zope 2.9.4.
Any ideas?
Have you looked at the code?
Yup, sure did. I can only guess that _setstate_noncurrent is called when the mvcc code decides it needs data from state that isn't the latest for an object. Unfortunately, neither of the asserts, including the failing one, have any comments anywhere near them. It's not at all clear what they're trying to protect again and I certainly have no idea why they might be tripping :-/ Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
participants (2)
-
Chris Withers -
Tres Seaver