Dieter Maurer schrieb:
Perry wrote at 2007-5-25 13:16 +0200:
database conflict error (oid 0x7905e6, class BTrees._IOBTree.IOBucket,
serial this txn started with 0x036ddc2a44454dee 2007-05-25
09:14:16.000950, serial currently committed 0x036ddc2c21950377
2007-05-25 09:16:07.870801) (80 conflicts
Joachim Schmitz schrieb:
I could reproduce the conflict error on my local machine not using ZEO.
I invoked the longrunning process "create_level" for two users after a
zope-restart.
here is the log:
2007-05-31 09:44:24 INFO Zope Ready to handle requests
2007-05-31 09:44:39 INFO Skins.create
>
> 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 star
Summary of messages to the zope-tests list.
Period Wed May 30 12:00:00 2007 UTC to Thu May 31 12:00:00 2007 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Wed May 30 20:52:11 EDT 2007
URL
Joachim Schmitz wrote at 2007-5-31 12:07 +0200:
> ...
>2007-05-31 09:45:06 INFO Skins.create_level A923157 finished to create
>level 200
>Now the conflict error, look at the transaction start-time, this is
>before the restart of zope !!
You are probably tricked out here: the serials are in fact
Dieter Maurer schrieb:
Joachim Schmitz wrote at 2007-5-31 12:07 +0200:
...
2007-05-31 09:45:06 INFO Skins.create_level A923157 finished to create
level 200
Now the conflict error, look at the transaction start-time, this is
before the restart of zope !!
You are probably tricked out here:
Hi,
I was able to locate the places in the Zope-sources where the conflict
error is triggered. On my local system it's in
ZODB.FileStorage in the store-method there is
if serial != cached_tid:
rdata = self.tryToResolveConflict(oid, cached_tid,serial, data)
in the tryToResolveConflict
>
> resolve object at 0xb28fff6c>>
> resolve object at 0xb1b81224>
> resolve object at 0xb1b81224>
> resolve object at 0xb260c80c>
> resolve object at 0xb260c614>
> resolve object at 0xb2a9146c>>
> resolve object at 0xb1b81224>
>
> The last resolve raises an exeption
>
> (Pdb) p sys.exc_i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maciej Wisniowski wrote:
>> resolve > object at 0xb28fff6c>>
>> resolve > object at 0xb1b81224>
>> resolve > object at 0xb1b81224>
>> resolve > object at 0xb260c80c>
>> resolve > object at 0xb260c614>
>> resolve > object at 0xb2a9146c>>
>> resolve > ob
