-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Withers wrote:
Chris McDonough wrote:
This is actually nothing to worry about. The error message doesn't take into account that the error it's reporting could be a conflict error (these are normal errors seen during Zope execution). The catalog probably shouldn't bother logging the error in this case.
Well, I think this has been fixed, but it's not so benign ;-) By catching a ConflictError like this, I'm pretty sure you can end up with inconsistent index state saved in your ZODB :-(
That method now has an explicit 'except ConflictError: raise' a few lines above the point which does the logging; I checked in that fix on 2005/07/05 (collector #1832). That fix was included in Zope 2.7.7 and in Zope 2.8.1. I would recommend that Marco upgrade to avoid the kind of consistency issues you point out. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDJXdR+gerLs4ltQ4RAme2AJ979YepexVREmLWKkC1TvQK3ib2rwCeOSlE X2S0SDfij1Xx+g4x3vZ5w+Q= =IyX7 -----END PGP SIGNATURE-----