[Zope-dev] Re: [Bug] ZODB invalidation processing

Maciej Wisniowski maciej.wisniowski at coig.katowice.pl
Thu May 31 07:47:23 EDT 2007


>
> I deleted the created objects and repeated the test:
>
> 2007-05-31 12:46:12 ERROR Zope.ZCatalog uncatalogObject unsuccessfully
> attempted to uncatalog an object with a uid of
> /uniben/campus/students/A923157/study_course/200/ZOO213.
> 2007-05-31 12:47:05 INFO Skins.create_level Y617041 started to create
> level 400
> 2007-05-31 12:47:14 INFO Skins.create_level A923157 started to create
> level 200
> 2007-05-31 12:47:25 INFO Skins.create_level Y617041 finished to create
> level 400
> 2007-05-31 12:47:40 INFO Skins.create_level A923157 finished to create
> level 200
> 2007-05-31 12:47:58 INFO ZPublisher.Conflict ConflictError at
> /uniben/campus/students/A923157/study_course/create_level: database
> conflict error (oid 0x3647b0, class BTrees._IOBTree.IOBucket, serial
> this txn started with 0x036dfe463486d955 2007-05-31 10:46:12.310958,
> serial currently committed 0x036dfe479a5725cc 2007-05-31
> 10:47:36.173536) (3 conflicts (0 unresolved) since startup at Thu May
> 31 09:44:24 2007)
>
> again the txn starttime is that of an older transaction, and it is the
> time of the uncatalog entry.
>
> If I invoke the create_level only for one student, no conflict-error
> occurs.
I've checked my logs for conflict errors with session machinery. I also had
times earlier than zope startup:

http://mail.zope.org/pipermail/zope-dev/2007-April/029244.html

I don't know why...

Maybe your problem is simply that 'create_level' does
something with Catalog (as Tres Seaver suggested).

If so, then if one transaction changes it
then second transaction raises conflict.

With sessions I had problems with OOBTree not IOBTree.

-- 
Maciej Wisniowski


More information about the Zope-Dev mailing list