Jim Fulton wrote at 2008-6-5 10:46 -0400:
On Jun 5, 2008, at 10:16 AM, Jim Fulton wrote:
On Jun 5, 2008, at 9:52 AM, David Otero Figueroa wrote:
I would like to know:
- Can conflict errors appear when reading objects from the ZODB?
Yes
Gaaa. I meant no.
Nevertheless, I think you have
On Jun 6, 2008, at 2:41 PM, Dieter Maurer wrote:
Jim Fulton wrote at 2008-6-5 10:46 -0400:
On Jun 5, 2008, at 10:16 AM, Jim Fulton wrote:
On Jun 5, 2008, at 9:52 AM, David Otero Figueroa wrote:
I would like to know:
- Can conflict errors appear when reading objects from the ZODB?
Yes
Previously David Otero Figueroa wrote:
Hello everyone,
I have a couple questions related to conflict errors.
During our home page stress testing (20 concurrent users), we detected
several conflict errors (see trace below), We thought these could ONLY
appear when writing objects in the
On Jun 5, 2008, at 10:16 AM, Jim Fulton wrote:
On Jun 5, 2008, at 9:52 AM, David Otero Figueroa wrote:
I would like to know:
- Can conflict errors appear when reading objects from the ZODB?
Yes
Gaaa. I meant no.
Jim
--
Jim Fulton
Zope Corporation
Tim Peters wrote:
I'm not really happy with that, because I have no theory for how ZEO
client cache files _get_ out of synch.
The most common one for me is connecting a ZEO client to one storage
server (say a dev one) and then changing the config to connect to
another storage server (say a
Paul Winkler wrote at 2005-2-24 15:16 -0500:
...
Twiddling around with some old suggestions from Dieter
Maurer (see
http://aspn.activestate.com/ASPN/Mail/Message/Zope-CMF/1978842 ),
I added a _p_jar.sync() where he suggested - right
before the final except: in initialize_product().
No joy.
Paul Winkler wrote at 2005-2-24 14:29 -0500:
This is a topic that comes up occasionally, but since the symptom
seems to be rare and hard to provoke, it never gets resolved.
Well it's biting me again and I'm determined to fix it, but
would like some input from the list.
I know that ZopeProfiler
ZODB.POSException.ConflictError: database conflict error (
serial this txn started with 0x035b25f36751f988 2005-02-10 18:59:24.215675,
serial currently committed 0x035b743c6d186822 2005-02-24 17:00:25.569220)
[Dieter Maurer]
Where is the oid in this ConflictError report?
It is vital
On Thu, Feb 24, 2005 at 02:29:50PM -0500, Paul Winkler wrote:
This is a topic that comes up occasionally, but since the symptom
seems to be rare and hard to provoke, it never gets resolved.
Well it's biting me again and I'm determined to fix it,
...
And since my ConflictError turned out to be
On Thu, Feb 24, 2005 at 02:29:50PM -0500, Paul Winkler wrote:
* Is the PIL stuff in the traceback a red herring or what?
Note that PIL is not referred to by anything in my Products
directory. (Heck, *nothing* is referred to by anything in Products.)
That's what's so baffling about it appearing
On Thu, Feb 24, 2005 at 02:52:45PM -0500, Chris McDonough wrote:
Two words: *hurt system*. Please, let me kill it.
Interesting. How on earth did you determine that?
You think it has to do with registering help for
PluginIndexes? I'm gonna go test that theory -
i'll hack registerHelp() to
On Thu, 2005-02-24 at 14:57, Paul Winkler wrote:
On Thu, Feb 24, 2005 at 02:52:45PM -0500, Chris McDonough wrote:
Two words: *hurt system*. Please, let me kill it.
Interesting. How on earth did you determine that?
Womanly intuition.
You think it has to do with registering help for
On Thu, Feb 24, 2005 at 02:58:01PM -0500, Chris McDonough wrote:
On Thu, 2005-02-24 at 14:57, Paul Winkler wrote:
On Thu, Feb 24, 2005 at 02:52:45PM -0500, Chris McDonough wrote:
Two words: *hurt system*. Please, let me kill it.
Interesting. How on earth did you determine that?
[Paul Winkler]
...
ZODB.POSException.ConflictError: database conflict error (
serial this txn started with 0x035b25f36751f988 2005-02-10 18:59:24.215675,
serial currently committed 0x035b743c6d186822 2005-02-24 17:00:25.569220)
No time here for thought, but those timestamps are two weeks
[Paul Winkler]
...
But - duh - my traceback clearly shows the ConflictError
happens before that, in the call to get_transaction().commit().
SO I moved the call to app._p_jar.sync() to right before hte call
to get_transaction().commit().
Aaaand... no more ConflictError.
Well, that's certain:
On Thu, Feb 24, 2005 at 03:16:15PM -0500, Paul Winkler wrote:
But - duh - my traceback clearly shows the ConflictError
happens before that, in the call to get_transaction().commit().
SO I moved the call to app._p_jar.sync() to right before hte call
to get_transaction().commit().
Aaaand... no
[Tim Peters]
...
Do you use a persistent ZEO client cache? If so, one thing to try is
to physically remove all the cache files -- maybe they've gotten into
an insane state.
Off list, Paul said bingo! to that one -- deleting his ZEO client
cache files apparently made the problem go away.
I'm
On Thu, Feb 24, 2005 at 04:11:35PM -0500, Tim Peters wrote:
[Tim Peters]
...
Do you use a persistent ZEO client cache? If so, one thing to try is
to physically remove all the cache files -- maybe they've gotten into
an insane state.
Off list, Paul said bingo! to that one -- deleting
Hi Chris, hi folks.
thanks for the hint with minimal storage. however the same problem
occurs with filestorage and is even worse.
we know very well, that we cannot avoid the appearance of conflict
errors in particular with zeo, and we understand what causes them.
what wonders us is, that we
On 18/05/2004, at 6:57 AM, Gerhard Schmidt wrote:
On Mon, May 17, 2004 at 01:38:15PM -0400, Chris McDonough wrote:
AFAIK Zope is the only appserver that even makes an attempt at
allowing
session data to be shared between servers like this. Most other
appservers require you to set up session
Hi Dr. Wagner,
thanks for the hint with minimal storage. however the same problem
occurs with filestorage and is even worse.
we know very well, that we cannot avoid the appearance of conflict
errors in particular with zeo, and we understand what causes them.
what wonders us is, that we
Gerhard Schmidt wrote at 2004-5-17 21:01 +0200:
...
However, due to a ZEO weakness, its conflict resolution
currently does not work (ZEO no longer supports INSTANCE_HOME).
Is that a bug or intetional.
I expect it to be a bug.
I plan to fix it soon -- but currently, I have lots of things to
On Mon, May 17, 2004 at 12:45:16PM -0400, Chris McDonough wrote:
On Thu, 2004-05-13 at 05:23, Gerhard Schmidt wrote:
Hi,
whe are running portal unter zope2.7 with one zeo server and six frontend
application servers.
I have set up zeo to server two storages
filestorage main
On Mon, 2004-05-17 at 13:06, Gerhard Schmidt wrote:
BDBMininalStorage is no longer maintained and doesn't do any conflict
resolution.
Why this. I was told some time ago we should use BDBMinimalStorage to
fix the conflict problems.
When was that and who told you so?
Even though
Gerhard Schmidt wrote at 2004-5-13 11:23 +0200:
...
Is there any why to get a shared session working.
You know that the ZODB is not designed for high frequency
concurrent writes?
When you want to reduce conflicts you will need to try hard
to minimize concurrent writes.
I have a (non-open)
On Mon, May 17, 2004 at 01:38:15PM -0400, Chris McDonough wrote:
On Mon, 2004-05-17 at 13:06, Gerhard Schmidt wrote:
BDBMininalStorage is no longer maintained and doesn't do any conflict
resolution.
Why this. I was told some time ago we should use BDBMinimalStorage to
fix the
On Mon, 2004-05-17 at 14:57, Gerhard Schmidt wrote:
Why isnt there an implementation of temporary storage for ZEO
There is, just use the tempstorage package from Zope.
I didnt find a way to use Tempstorage in zeo.
temporarystorage
name temporary storage for sessioning
Bjorn Stabell wrote:
In any case, is there no way to find out more detailed information about
why a conflict happened? There must be some oids somewhere?
I don't know of a way. In a conflict, the transaction gets aborted, so
the only data left is the log entry.
Shane
Bjorn Stabell wrote at 2003-6-3 11:08 +0800:
Except for SARS, another problem that's been plagueing us for months are
seemingly random Conflict Errors. We see about 10 every day on our Zope
2.6.1, and they can happen on any page. In most cases they are not
related to pages that actually
Dieter Maurer wrote:
The attached patch to Zope/App/startup.py provides this
additional information.
Where's the patch?
cheers,
Chris
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
Chris Withers wrote:
Dieter Maurer wrote:
The attached patch to Zope/App/startup.py provides this
additional information.
Where's the patch?
http://marc.theaimsgroup.com/?l=zope-devm=105466926610469q=p3
--
Jamie Heilman http://audible.transient.net/~jamie/
I was in
On 06/02/2003 11:08 PM, Bjorn Stabell wrote:
Hi all,
Except for SARS, another problem that's been plagueing us for months are
seemingly random Conflict Errors. We see about 10 every day on our Zope
2.6.1, and they can happen on any page. In most cases they are not
related to pages that actually
On 06/02/2003 11:08 PM, Bjorn Stabell wrote:
Except for SARS, another problem that's been plagueing us for months
are seemingly random Conflict Errors. We see about 10 every day on
our Zope 2.6.1, and they can happen on any page. In most cases
they
are not related to pages that
Chris Withers writes:
However, if anyone does know what constitutes a 'seperate object' in
ZODB terms, it be really useful to know.
I'm guessing a class which inherits from Persistent? Dictionaries don't,
'cos they're python builtins, which I'm pretty certain was the problem
in my
On Tue, 02 Jan 2001 16:50:49 +, Chris Withers [EMAIL PROTECTED]
wrote:
However, if anyone does know what constitutes a 'seperate object' in
ZODB terms, it be really useful to know.
I'm guessing a class which inherits from Persistent? Dictionaries don't,
'cos they're python builtins, which
Chris McDonough wrote:
The ZODB tries
hard to avoid error conditions for you by retrying conflicting writes, but
if you really pound the snot out of a particular object, it'll let you know.
That's gotta be one for the Zope quotes board, if I could onyl remember
the URL :-)
and step
TECTED]
Sent: Tuesday, January 02, 2001 11:50 AM
Subject: Re: [Zope-dev] Conflict Errors
Chris McDonough wrote:
The ZODB tries
hard to avoid error conditions for you by retrying conflicting writes,
but
if you really pound the snot out of a particular object, it'll let you
know.
That's go
Chris Withers wrote:
i'm no expert but deeply nested data structures in a single object are
rife with possibilities for conflict errors. if data might be changing
concurrently in the structures or frequently changing you would be
better off to switch the structure to nested persistent objects.
On Tue, 21 Nov 2000 17:03:17 +, Chris Withers [EMAIL PROTECTED]
wrote:
It happens when more than one thread tries to modify the same object in
storage at the same time. It's Zope's equivalent of record-locking... It's
normal. There's no corruption or anything, it's telling you that it
Hurm, well, it appears to happen when we're doing a lot of sequential
write to a product (automated bulk data upload), but the thing that
triggers it off is actually trying to read a page from the same area of
the site... confusing. Although that could also be a one-off
coincidence...
It happens when more than one thread tries to modify the same object in
storage at the same time. It's Zope's equivalent of record-locking... It's
normal. There's no corruption or anything, it's telling you that it avoided
a write that might have caused problems. Zope tries three times to
41 matches
Mail list logo