Answering to myself:
we could get rid of the sessionrelated conflict errors, by removing all
session = context.REQUEST.SESSION
from our scripts. But we still have these conflict errors:
how can I find out, what causes these conflicts.
2007-05-25T10:17:50 INFO ZPublisher.Conflict
Summary of messages to the zope-tests list.
Period Thu May 24 12:00:00 2007 UTC to Fri May 25 12:00:00 2007 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Thu May 24 20:59:43 EDT 2007
Perry napisał(a):
Answering to myself:
we could get rid of the sessionrelated conflict errors, by removing all
session = context.REQUEST.SESSION
from our scripts. But we still have these conflict errors:
how can I find out, what causes these conflicts.
2007-05-25T10:17:50 INFO
Maciej Wisniowski schrieb:
Perry napisał(a):
Answering to myself:
we could get rid of the sessionrelated conflict errors, by removing all
session = context.REQUEST.SESSION
from our scripts. But we still have these conflict errors:
how can I find out, what causes these conflicts.
I set it now to 9600/4800 (Timeout/Resolution) but it seams that it has
no effect.
Hm... where did you set this? At faster's preferences page in ZMI?
can you verify that these settings are used?
To change timeout/resolution to high values for standard session
implementation in zope.conf I had to
Maciej Wisniowski schrieb:
I set it now to 9600/4800 (Timeout/Resolution) but it seams that it has
no effect.
Hm... where did you set this? At faster's preferences page in ZMI?
Yes
can you verify that these settings are used?
don't know how.
To change timeout/resolution to high values for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Perry wrote:
Answering to myself:
we could get rid of the sessionrelated conflict errors, by removing all
session = context.REQUEST.SESSION
from our scripts. But we still have these conflict errors:
how can I find out, what causes these
Perry wrote at 2007-5-25 13:16 +0200:
database conflict error (oid 0x7905e6, class BTrees._IOBTree.IOBucket,
serial this txn started with 0x036ddc2a44454dee 2007-05-25
09:14:16.000950, serial currently committed 0x036ddc2c21950377
2007-05-25 09:16:07.870801) (80 conflicts (10 unresolved) since
