----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "Jonathan" <[EMAIL PROTECTED]>
Cc: "Dennis Allison" <[EMAIL PROTECTED]>; <firstname.lastname@example.org>
Sent: Wednesday, July 05, 2006 2:28 PM
Subject: Re: [Zope] Trying to trap ConflictError
Jonathan wrote at 2006-7-4 13:46 -0400:
The image objects stored in
TemporaryStorage are never overwritten, edited etc (which is causing me
confusion as to why the conflict errors are occurring)
The error message tells your that the conflict is not caused by
the modification of the image but the container holding your image.
"BTreeFolder" already do conflict resolution -- and reduce the
conflict probability by about a factor of 30 to 100 (depending on type).
However, if several threads should try to add elements with the same
id, then the conflict resolution cannot work.
Maybe, that happens in your case?
The id for the image object is generated by the following code:
ts = string.replace(str(time.time()),'.', '') # remove floating point
So there should not be any collision of ids.
I am still investing, and have found errors like:
2006-07-04T14:48:12 ERROR ZODB.Connection Couldn't load state for 0x1c
Traceback (most recent call last):
File "/usr/local/Zope-2.9.2/lib/python/ZODB/Connection.py", line 732, in
File "/usr/local/Zope-2.9.2/lib/python/ZODB/Connection.py", line 768, in
p, serial = self._storage.load(obj._p_oid, self._version)
line 104, in load
in the event.log. From my googling research, it appears that these type of
errors may be due to insufficient memory (but I am not sure and am still
investigating to see if this is the cause of the conflict errors).
Thanks to all for the suggestions and assistance!
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -