Berthold Stöger wrote at 2006-6-29 20:35 +0200:
>On Thursday 29 June 2006 18:56, Dieter Maurer wrote:
>> Good application design would make the conflict probability so low
>> that it is very unlikely that a "ConflictError" propagates to
>> the user.
>
>For more complicated applications this is onl
- Original Message -
From: "Berthold Stöger" <[EMAIL PROTECTED]>
To:
Cc: "Dieter Maurer" <[EMAIL PROTECTED]>
Sent: Thursday, June 29, 2006 2:35 PM
Subject: Re: [Zope] ConflictError with *one* ZEO client?
On Thursday 29 June 2006 18:56, Dieter Maurer
On Thursday 29 June 2006 18:56, Dieter Maurer wrote:
> Good application design would make the conflict probability so low
> that it is very unlikely that a "ConflictError" propagates to
> the user.
For more complicated applications this is only possible with locking. Does
Zope provide locking pr
Richard Jones wrote at 2006-6-29 08:29 +1000:
> ...
>Since we upgraded to 2.8 we see a few ConflictErrors propogated up through to
>users each week.
Usually, this means weak application design.
Good application design would make the conflict probability so low
that it is very unlikely that a "Co
On Thursday 29 June 2006 06:13, Dieter Maurer wrote:
> Richard Jones wrote at 2006-6-28 11:24 +1000:
> >it crashes out with a ConflictError even if there are no other ZEO clients
> >connected to the ZEO store.
>
> Usually, a "ConflictError" does not crash Zope...
Sure, we requests are retried, but
Richard Jones wrote at 2006-6-28 11:24 +1000:
>it crashes out with a ConflictError even if there are no other ZEO clients
>connected to the ZEO store.
Usually, a "ConflictError" does not crash Zope...
In the past, I have seen occational "ConflictError" during
product initialization (some bug).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28 Jun 2006, at 11:13, Richard Jones wrote:
On Wednesday 28 June 2006 18:31, Jens Vagelpohl wrote:
Are you using persistent ZEO caches? Those have been known to cause
odd symptoms here and there...
What do you mean by "persistent"? I have not
On Wednesday 28 June 2006 18:31, Jens Vagelpohl wrote:
> Are you using persistent ZEO caches? Those have been known to cause
> odd symptoms here and there...
What do you mean by "persistent"? I have noticed strange beahviours if I don't
remove the caches when I do a full (client + server) restart
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28 Jun 2006, at 10:23, Richard Jones wrote:
If you're running a script you should tell us what the script does.
The script merely modified a bunch of objects in the ZODB. Beyond
that,
there's not much that I can usefully tell you.
I'm using
On Wednesday 28 June 2006 18:12, Jens Vagelpohl wrote:
> On 28 Jun 2006, at 03:24, Richard Jones wrote:
> > I've got a zopectl script I'm trying to run with the "zopectl run"
> > command. It
> > crashes out with a ConflictError even if there are no other ZEO
> > clients
> > connected to the ZEO sto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28 Jun 2006, at 03:24, Richard Jones wrote:
I've got a zopectl script I'm trying to run with the "zopectl run"
command. It
crashes out with a ConflictError even if there are no other ZEO
clients
connected to the ZEO store. I've restarted the
On Wednesday 28 June 2006 11:35, you wrote:
> Which Zope are you using? Set the logging level to BLATHER and try
> running with runzope rather than zopectl and see what happens. The
> event log should help localize the problem. Be sure to check both the
> ZEO logs and the Zope logs.
>
> Also, i
Which Zope are you using? Set the logging level to BLATHER and try
running with runzope rather than zopectl and see what happens. The
event log should help localize the problem. Be sure to check both the
ZEO logs and the Zope logs.
Also, it helps if you post the traceback.
On Wed, 28 Jun
I've got a zopectl script I'm trying to run with the "zopectl run" command. It
crashes out with a ConflictError even if there are no other ZEO clients
connected to the ZEO store. I've restarted the ZEO store, no change.
Any advice? Ideas?
Richard
___
14 matches
Mail list logo
