Tres Seaver schrieb:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
------ 2007-05-25T10:19:01 ERROR Zope.SiteErrorLog http://uniben.waeup.org/campus/students/C172676/study_course/create_level Traceback (innermost last): Module Zope2.App.startup, line 173, in zpublisher_exception_hook Module ZPublisher.Publish, line 121, in publish Module Zope2.App.startup, line 240, in commit Module transaction._manager, line 96, in commit Module Products.CPSCompat.PatchZODBTransaction, line 175, in commit Module transaction._transaction, line 436, in _commitResources Module ZODB.Connection, line 665, in tpc_vote Module ZEO.ClientStorage, line 893, in tpc_vote Module ZEO.ClientStorage, line 877, in _check_serials ConflictError: database conflict error (oid 0x7905e6, class BTrees._IOBTree.IOBucket, serial this txn started with 0x036ddc2b3e989fdd 2007-05-25 09:15:14.670982, serial currently committed 0x036ddc2dd48f4e33 2007-05-25 09:17:49.818700)
Neither of those tracebacks look like they come out of the 'faster' session machinery itself; it uses an 'OOBTree' by default for storing the slices, not an 'IOBtree'. The primary consumer of 'IOBTree' is probably the catalog, where it is used to map RID -> values in the 'unindex' of 'FieldIndex', etc. The original sessioning machinery uses 'IOBTree', too: are you sure you are using the faster machnery?
Yes, but I am not sure, or better I don't know who is causing these errors. -- Gruß Joachim