this sounds like a zope/plone problem not a ZODB problem.
might want to ask on the relevant mailing list
On Thu, Jun 5, 2008 at 5:10 AM, David Otero Figueroa <[EMAIL PROTECTED]> wrote:
>
>
> Hello everyone,
>
> I have a couple questions related to "conflict errors".
>
> During our home page stress
On Jun 5, 2008, at 6:10 AM, David Otero Figueroa wrote:
...
I would like to know:
- Can conflict errors appear when reading objects from the ZODB?
No
- Could conflict errors be the cause of a "spinning ZOPE" scenario?
- Is there any situation where ZOPE could try to write objects when
re
Hello Marco,
I have this problems too in a not estress testing. In a simple access (2
concurrents users) I have this response:
2008-05-27T13:23:48 INFO ZODB conflict error at /portal/ (22 conflicts since
startup at 2008-05-27T10:37:28)
2008-05-27T13:23:48 INFO ZODB conflict error at /portal/ (23
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 ZODB.
2008-05-27T18:57:53 INFO ZODB conflict
Sidnei da Silva wrote:
On Thu, Mar 02, 2006 at 02:28:50PM -0300, Sidnei da Silva wrote:
| Hi there,
|
| I'm facing an issue with a ConflictError that won't go away even after
| restarting. Looks like the ZODB got screwed somehow. Here's the
| traceback:
False alarm. The zeo cache was just in a
On Thu, Mar 02, 2006 at 02:28:50PM -0300, Sidnei da Silva wrote:
| Hi there,
|
| I'm facing an issue with a ConflictError that won't go away even after
| restarting. Looks like the ZODB got screwed somehow. Here's the
| traceback:
False alarm. The zeo cache was just in an unusual place so I didn'
Wherever I run ZEO I would never enable the persistent cache. It has
always tended to create more problems than it solves.
I think a lot of people don't realize that the "persistent" of
"persistent cache" only means "survives across ZEO client restarts",
not "enable the ZEO cache". The ZEO
We've also seen this problem related to corrupted caches.
Dennis Allison wrote:
> We've seen this problem occasionally. Usually deleting the ZEO cache
> clears the problem.
>
>
> On Thu, 2 Mar 2006, Sidnei da Silva wrote:
>
>
>>Hi there,
>>
>>I'm facing an issue with a ConflictError that won
On Thu, Mar 02, 2006 at 09:37:02AM -0800, Dennis Allison wrote:
|
| We've seen this problem occasionally. Usually deleting the ZEO cache
| clears the problem.
Except it didn't seem to resolve the problem in this case, that's why
I'm confused.
--
Sidnei da Silva
Enfold Systems, LLC.
http://en
On 2 Mar 2006, at 17:28, Sidnei da Silva wrote:
Hi there,
I'm facing an issue with a ConflictError that won't go away even after
restarting. Looks like the ZODB got screwed somehow. Here's the
traceback:
Have you read this document and tried some of the tools mentioned here?
http://www.zo
We've seen this problem occasionally. Usually deleting the ZEO cache
clears the problem.
On Thu, 2 Mar 2006, Sidnei da Silva wrote:
> Hi there,
>
> I'm facing an issue with a ConflictError that won't go away even after
> restarting. Looks like the ZODB got screwed somehow. Here's the
> trace
Hi there,
I'm facing an issue with a ConflictError that won't go away even after
restarting. Looks like the ZODB got screwed somehow. Here's the
traceback:
* Module Zope.App.startup, line 163, in zpublisher_exception_hook
* Module ZPublisher.Publish, line 107, in publish
* Module Zope
Antonio Beamud Montero wrote:
Where Status is a Persistent Class, with an OOBTree attribute called
_dict, and serveral methods wrapping this _dict, like add, remove, etc..
OOBTree's have conflict resolution code which will try and do the right
thing instead of raising a ConflictError...
Whe
Hi all:
I have a problem with conflicts in my system. I have implemented a
multi-thread server and I have several server as ZEO clients.
In ZODB I have created 3 objects:
root['pendings'] = Status()
root['error'] = Status()
root['completed'] = Status()
Where Status is a Persistent Class, with an
14 matches
Mail list logo
