On 5/31/07, Joachim Schmitz [EMAIL PROTECTED] wrote:
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,
Hi!
We have one ZEO server that handles 3 FileStorages and 8 ZEO clients
connecting to the ZEO server.
Sometimes a client hangs and does no longer handle incoming connections.
The ZEO server log shows in such a case, that the (hanging) client
initiates a new connection
2006-11-12T10:30:39
On 6/3/06, Dieter Maurer [EMAIL PROTECTED] wrote:
A ZEO weakness, I fixed in our local copy this way:runzeo.py:try: from App import FindHomesexcept ImportError: pass # this is not Zope
This works for me.
Thanks!
-- Markus
___
Zope-Dev maillist -
into the ZEOinstance. At least those Products it tries to load for conflictresolution.HTH,StefanOn 2. Jun 2006, at 10:21, M. Krainer wrote:
How can I teach the zeo server to lookup my Products dir to resolve the conflict?--Anything that happens, happens.--Douglas Adams
http://www.zope.org/Collectors/Zope/2042Is there a chance that this will make it into the Zope-2.8.7 release?-- Markus
On 3/9/06, Dieter Maurer [EMAIL PROTECTED] wrote:
Jim Fulton wrote at 2006-3-8 10:46 -0500:Dieter Maurer wrote: The ZODB allows to include the class (a reference to it) into
1. Do you want these ConflictErrors retried logs to be at level:INFO
2. In addition, please specify if you feel those retriedConflictErrors should have their full traceback logged?
no, without traceback 3. Finally, please tell us if the ConflictErrors that *can't* be
retried (and are returned to
Hi!
Is there a possibility to cutpaste from one mounted storage to another?
I have a filestorage Data.fs mounted as / and another filestorage
Archive.fs mounted at /site/Archive. When I try to cutpaste an
object from e.g. /site/foo/bar to /site/Archive/bar I get an
InvalidObjectReference
Hi!
We run a self developed zope product originally based on cmf but
highly customized and extended. Our Data.fs now has grown to a
(packed) size of 25GB and we are running more and more into
performance troubles (mostly due to a lot of conflict errors). Our
users make a lot of updates, i.e. we
