On 4/12/07, Maciej Wisniowski [EMAIL PROTECTED] wrote:
Hi
Currently I have some problems with our application (Zope2.8.4)
and with Conflict Errors in sessions.
In general if we have few concurrent requests that are running
sometimes for 3-4 minutes (and they're touching session inside)
I get a
On 4/6/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi,
I have inherited an existing buildout architecture developed in-house
which is becoming difficult to support and maintain. There are about
25 setup tasks in total. I am considering moving it to using
zc.buildout. Two questions:
- is
On 2/3/07, yacine chaouche [EMAIL PROTECTED] wrote:
I am experiencing issues regarding a database ConflictError on session objects.
Can you detail all the various getSesion and setSession methods of:
http://mail.zope.org/pipermail/zope/2007-January/170167.html
I use zope 2.9.0 python
On 10/29/06, Yoshinori Okuji [EMAIL PROTECTED] wrote:
IIRC, Jim noted that it would be better to
backport zope3's, while our patches are for zope2's.
See http://mail.zope.org/pipermail/zope-dev/2006-May/027503.html for a
short thread on successfully using xmlpickle. With that recipe and
patch
On 9/1/06, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I'm getting a ZODB.POSException.ConflictError in the following code in a
Custom Zope Product, and I'm hoping someone can enlighten me on how to
fix it.
# nd is a folder with a sub-folder Categories
# NDCategory is a custom Zope product I
From what I can tell the feature that is Hotfixed does not appear
until Zope 2.7.3. If the Hotfix is installed in Zope 2.7.0 through to
2.7.2 then it shows up as a broken product. No real harm done.
The product import breaks with:
Traceback (most recent call last):
File
On 7/14/06, Philip Kilner [EMAIL PROTECTED] wrote:
For the last three days, we have been plagued by slowdowns and temporary
lock-ups, which have on a couple of score occasions culminated in a
Conflict Error, indicting transactional problems in the temporary
storage. On four or five occasions,
On 7/7/06, Jonathan [EMAIL PROTECTED] wrote:
I haven't been able to determine how the oid's are generated, other than
little-endian 64-bit unsigned integers that will be assigned more or less
sequentially, but I can't figure out how the same oid is being used twice
(on the other hand I could be
On 7/7/06, Michael Dunstan [EMAIL PROTECTED] wrote:
An oid is an identifier for a persistent state of an object. As the
state of an object evolves from transaction to transaction it gets a
new oid for each state. Two concurrent transactions that involve the
same object will start with the same
On 7/6/06, Jonathan [EMAIL PROTECTED] wrote:
I am still investing, and have found errors like:
2006-07-04T14:48:12 ERROR ZODB.Connection Couldn't load state for 0x1c
Traceback (most recent call last):
File /usr/local/Zope-2.9.2/lib/python/ZODB/Connection.py, line 732, in
setstate
On 5/26/06, Jim Fulton [EMAIL PROTECTED] wrote:
It would be nice to integrate this back into the export/import
machinery.
Yeah, I'd like to think I'll be able to find time to put this into Zope 2.11.
Any suggestions on getting a successful dumps of a Missing.Value?
You need someone with
On 1/20/06, Tim Peters [EMAIL PROTECTED] wrote:
In all, zope.testing is a poster child for the value of package
development outside of a Zope tree.
I've been very happy using zope.testing with several non zope
projects. Including how easy it is to follow and distribute that
package as needed
On 12/22/05, Dennis Allison [EMAIL PROTECTED] wrote:
The issue here has had to do with session variables and their iteraction
with the persistence mechanism and conflicts and multiple threads for the
same session. Chris McDonough has pointed out that session variables can
cause writes and
On 12/19/05, Jan-Ole Esleben [EMAIL PROTECTED] wrote:
1. In the example, just setting _p_changed=1 does _not_ lead to a
conflict error. With the ineffectual code above it (that never gets
executed) it _does_. So there _is_ some implicit magical stuff going
on and ZOPE tries to take
On 12/19/05, Jan-Ole Esleben [EMAIL PROTECTED] wrote:
Little bit tricky to try out as testers need to guess what all the
missing code is.
Any standard persistent ZOPE product wrapped around this will do.
These are the only methods in a ZOPE product that inherits from Item,
Persistent,
On 12/16/05, Dennis Allison [EMAIL PROTECTED] wrote:
MAYBE CONFLICTS AND THEIR RESOLUTION ARE NOT THE ROOT CAUSE OF THE SESSION
VARIABLE PROBLEM. The observed problem is that session variables suddenly
disappear.
Perhaps your app is tripping over some bug in conflict handling. But
I'd say it
On 12/9/05, Dennis Allison [EMAIL PROTECTED] wrote:
The problem I am trying to resolve appears to be load related. The
observed symptom is that (some) session variables spontaneously disappear.
There appears to be some connection to conflicts, but the exact mechanism
and the relationship is
On 12/11/05, Dennis Allison [EMAIL PROTECTED] wrote:
Good idea, but it is hard to do in a production environment with a never
lose data model.
Have a go at recreating the problems you are seeing on a development
host. SessionRig can be used to mount a brute force attack of the
session
How about adding a URL to the logged message? Something like
See http://zope.org/ConflictError;
detailing the difference between a retried and unresovled
ConflictErrors and how to recognise them in the event.log.
___
Zope-Dev maillist -
On 11/18/05, Chris McDonough [EMAIL PROTECTED] wrote:
On Nov 17, 2005, at 4:46 AM, Dennis Allison wrote:
Thank Chris, good pointsB.
The session variable timeout is currently several hours as requird
by our
application. The timeout resolution remains at its default value.
Making
On 8/28/05, Dan Gaibel [EMAIL PROTECTED] wrote:
Hi folks,
This is my first post to this list and I'm desperate for help. I'm running
Zope 2.6.1 with Python 2.1.3. My Zope instance died today and won't come
back. When I try to start it, I get:
2005-08-27T20:58:15 PANIC(300) z2 Startup
On 8/22/05, Tres Seaver [EMAIL PROTECTED] wrote:
Are we sure that we won't be breaking the rather large possible set of
installed servers running behind Apache 1.3.x with the bug for which
adding the content length was a workaround?
I understand that this bug was resolved in Apache 1.3.27 [1].
On 2005-08-18, at 06:35 GMT+12:00, Bernd Dorn wrote:
On 17.08.2005, at 20:22, Garito wrote:
Hi again!
Sorry but Zope is executable, perhaps another thing?
Any idea?
hm, have you set the effective user in zope.conf? you need this if
you run zopectl as root
as root try to execute
On 22/06/2005, at 4:50 AM, Leticia Larrosa wrote:
Hi:
Thanks to Michael Dunstan. I test with the recomendation of
Michael but I still get the error. In pages where I get the error,
if I wait some seconds and refresh the pages, I obtain the correct
information (no get the error).
I
Hi Leticia,
The mixture of ``response.write()`` including JavaScript to drive the
browser to a new location along with writing objects in ZODB all
within the same transaction can break some of the promises that you'd
normally expect Zope and a browser to keep.
My guess is that browser is
I'm seeing test failures in transience when running the tests for
Zope-2_7-branch (python 2.3.3) with garbage collection threshold0 set
to 1.
Seems to break in slightly different places from run to run. Here is
one example:
% python test.py -vv --dir lib/python/Products/Transience/tests -g
On 6/10/2004, at 4:06 AM, Tim Peters wrote:
[Michael Dunstan]
I'm seeing test failures in transience when running the tests for
Zope-2_7-branch (python 2.3.3) with garbage collection threshold0 set
to 1.
snip
Whenever I see a test module import fauxtime, I run screaming in
terror. This seems
On 29/09/2004, at 11:07 AM, Matteo Memelli wrote:
Hello I include the conversation that I had today with Chris:
I'm using Zope 2.6b1+ with ZWarehouse e-commerce product
(ZWarehouse-20040522 version 0.8)
I tried upgrading to Zope 2.7 but ZWarehouse gave me many problems so
I decided to try applying
On 25/08/2004, at 12:55 AM, Florent Guillaume wrote:
I've reopened bug 789 (http://collector.zope.org/Zope/789) because we
observed problems in Zope 2.7.2 with transaction abort by the
publisher.
The problems can make objects disappear or provoke POSKeyErrors.
Here is a patch for publisher that
On 12/07/2004, at 12:29 PM, Chris McDonough wrote:
FWIW, as far as I understand the prevent commit on conflict behavior
*is* currently the behavior for caught ReadConflictErrors. The only
time ZODB doesn't exhibit this behavior is *during the commit of a
transaction*. If a commit is attempted at
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
On 18/05/2004, at 10:03 PM, Andrea Patuzzo wrote:
Hi, dear developers:
We are now randomly getting this kind of error:
[...]
File
/usr/local/Zope270CVS/lib/python/Products/Transience/Transience.py,
line 341, in __setitem__
current_bucket = self._data[current_ts]
KeyError: 1084872640
On 19/05/2004, at 8:36 AM, Chris McDonough wrote:
As a result, I am coming to believe that along with the errors as part
of main transaction patch for 2.7.1, I should also make the
retry-on-conflict-error policy pluggable for those who really
desperately need to slow their Zope systems to a
On 18/05/2004, at 5:42 AM, Chris McDonough wrote:
On Mon, 2004-05-17 at 13:06, Steve Jibson wrote:
Also of note:
1 - After having the system run for 45 minutes, I had 8 similar
errors.
Some were on different web pages and some had different keys that
were causing the error.
2 - I have also
On 14/05/2004, at 10:06 AM, Chris McDonough wrote:
I am tempted to check the following into the 2.7 branch and HEAD:
- error occurs in same transaction as main request patch
to Publish.py. See
http://www.plope.com/Members/chrism/
publishpy_errorinmaintrainsaction.patch/file_view
for the
On 11/05/2004, at 4:54 PM, Chris McDonough wrote:
On Mon, 2004-04-26 at 18:34, Michael Dunstan wrote:
I removed all the above hacks leaving just the
one that comments out the construction of the to_notify list. Reran
the
test rig. And have yet to see any KeyErrors.
Have you seen any since
On 7/05/2004, at 5:15 AM, Kris Erickson wrote:
No, that's not the problem;
in THEORY that's what is happening, but in reality there is no way
that this is the case;
We just unrolled a registration system with participation rates at or
around 100 to 200 participants per month;
At any given time,
On 7/05/2004, at 4:39 PM, Tres Seaver wrote:
Michael Dunstan wrote:
On 7/05/2004, at 5:15 AM, Kris Erickson wrote:
No, that's not the problem;
in THEORY that's what is happening, but in reality there is no way
that this is the case;
We just unrolled a registration system with participation rates
On 11/03/2004, at 7:25 PM, Chris McDonough wrote:
On Wed, 2004-03-10 at 23:14, michael wrote:
Thanks for your excellent isolation here.
I don't get a KeyError thrown until *after* at least one rendering of
standard_error_message that includes an access to a session variable.
And I'm only
On 31/03/2004, at 7:31 AM, Tres Seaver wrote:
Overall, I agree with you that stylesheets are best kept static.
However, consider what happens to cacheability when the URLs of of
images referenced in a document are relative; the same problem can
afflict stylesheets, particularly in a setup
40 matches
Mail list logo
