Re: [Zope-dev] Debugging conflict errors? Hints please!
Thanks Jeremy, but could you speak more slowly please? ;-) Which debug log are you refering to? There is nothing in the stupid log, and Big M logging does also not give me any indication of conflicts or oids. Do I have to run everything inside pdb? I also do not seem to figure out where the ConflictErrors are raised. I have added log messages to every single occurrence of raise ConflictError in lib/python/ZODB/* but I never see any of them... Stefan --On Freitag, 11. Oktober 2002 11:15 -0400 Jeremy Hylton [EMAIL PROTECTED] wrote: SHH == Stefan H Holek [EMAIL PROTECTED] writes: The debug log should show the oid that caused the conflict error. From the oid, you ought to be able to figure out what the object is -- class, etc. -- and then what transactions have modified that object. Can anyone recommend a simple strategy for either of these two steps? There's got to be a good way to do it, but I'm not sure what the best way is. I'd open the database in an interactive prompt: db.open()[oid] That would get me the object. Then I'd use fsdump to find all the transactions that include that oid. That would be a very manual process since I'd just grep the textual dump of the storage. Jeremy -- Those who write software only for pay should go hurt some other field. /Erik Naggum/ ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Debugging conflict errors? Hints please!
SHH == Stefan H Holek [EMAIL PROTECTED] writes:
SHH Hi All! I am experiencing a lot of 'ZODB conflict error at
SHH ...' that I can reliably reproduce by hitting my browser's
SHH Refresh button at a high rate. The bad news is that the
SHH conflicts happen on pages that are not supposed to change
SHH anything in the ZODB but only display results of some SQL
SHH queries. My question is now how to find out what actually is
SHH causing the conflicts. The log entry refers to the page being
SHH served ('/very/long/path/detail_view').
The debug log should show the oid that caused the conflict error.
From the oid, you ought to be able to figure out what the object is --
class, etc. -- and then what transactions have modified that object.
Can anyone recommend a simple strategy for either of these two steps?
There's got to be a good way to do it, but I'm not sure what the best
way is. I'd open the database in an interactive prompt:
db.open()[oid]
That would get me the object. Then I'd use fsdump to find all the
transactions that include that oid. That would be a very manual
process since I'd just grep the textual dump of the storage.
Jeremy
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Debugging conflict errors? Hints please!
conflict errors do not imply conflicting writes by definition. there is
a thing called read conflict, which is probably what happens to you.
jens
On Friday, Oct 11, 2002, at 07:47 US/Eastern, Stefan H. Holek wrote:
Hi All!
I am experiencing a lot of 'ZODB conflict error at ...' that I can
reliably reproduce by hitting my browser's Refresh button at a high
rate. The bad news is that the conflicts happen on pages that are not
supposed to change anything in the ZODB but only display results of
some SQL queries. My question is now how to find out what actually is
causing the conflicts. The log entry refers to the page being served
('/very/long/path/detail_view').
As a matter of fact I am not even sure whether the log entry means
that the 'detail_view' document has changed (which of course it
hasn't), or something along the traversal path caused a ZODB write.
Zope 2.5.1, ZEO 1.0
Any hints on how I could find the culprit appreciated.
Thanks,
Stefan
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Debugging conflict errors? Hints please!
Yes, but AFAIK read conflicts mean that something has changed during a read. I do not expect this to happen either... Stefan --On Freitag, 11. Oktober 2002 07:54 -0400 Jens Vagelpohl [EMAIL PROTECTED] wrote: conflict errors do not imply conflicting writes by definition. there is a thing called read conflict, which is probably what happens to you. jens -- Those who write software only for pay should go hurt some other field. /Erik Naggum/ ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
