Re: [Zope-dev] Conflict errors on startup, revisited

2005-02-24 Thread Paul Winkler
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 -

Re: [Zope-dev] Conflict errors on startup, revisited

2005-02-24 Thread Tim Peters
[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.

Re: [Zope-dev] Conflict errors on startup, revisited

2005-02-24 Thread Paul Winkler
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...

Re: [Zope-dev] Conflict errors on startup, revisited

2005-02-24 Thread Tim Peters
[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 cer

Re: [Zope-dev] zope and python2.3.5

2005-02-24 Thread Dieter Maurer
Andreas Jung wrote at 2005-2-21 21:33 +0100: > ... >> Maybe zope configure shouldnt stop on newer, but from the same branch, >> version of python? > >Things are as they are and it is exhausting to discuss about advantages and >disadvantages. >Python 2.3.5 will be officially recognized by Zope 2.7.

Re: [Zope-dev] Conflict errors on startup, revisited

2005-02-24 Thread Tim Peters
[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

Re: [Zope-dev] Conflict errors on startup, revisited

2005-02-24 Thread Paul Winkler
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

Re: [Zope-dev] Conflict errors on startup, revisited

2005-02-24 Thread Chris McDonough
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 fo

Re: [Zope-dev] Conflict errors on startup, revisited

2005-02-24 Thread Paul Winkler
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 no-op

Re: [Zope-dev] Conflict errors on startup, revisited

2005-02-24 Thread Paul Winkler
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 i

Re: [Zope-dev] Conflict errors on startup, revisited

2005-02-24 Thread Chris McDonough
Two words: *hurt system*. Please, let me kill it. On Thu, 2005-02-24 at 14:29, 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, but > wo

[Zope-dev] Conflict errors on startup, revisited

2005-02-24 Thread Paul Winkler
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. Related collector issues: http://www.zope.org/Collectors/Zope/300 http://