Andre Schubert wrote at 2003-3-28 10:15 +0100:
 > i have a little problem with the following log-entry in my logfile.
 > 
 > 2003-03-28T10:09:18 INFO(0) ZODB conflict error at /foo/bar/tab_kopf (1 conflicts 
 > since startup at 2003-03-28T10:09:03).
 > 
 > After searching through several mailinglists i found that this
 > error seem to occur when using sessions, i'am right ?
 > But my problem is, that tab_kopf is a ImageFile defined in my Product.
 > 
 > tab_kopf = ImageFile('www/tab_kopf.gif',globals())
 > 
 > I dont understand how there could be a ConflictError on a Image ?
 > I hope someone could give me a tip whats going on.

Please file a feature request to "<http://collector.zope.org/Zope>".
Zope should distinguish between "Write" and "Read conflict errors".
You can try the necessary modification yourself. Patch
for Zope 2.6.1 attached.

You probably see a "Database read conflict error".
It may happen for reading "foo", "bar" or "tab_kopf".
The patch will give you hints what object got this error.


Dieter

--- Zope/App/startup.py~	2003-02-28 16:59:25.000000000 +0100
+++ Zope/App/startup.py	2003-03-17 11:13:28.000000000 +0100
@@ -140,9 +140,9 @@
                 global conflict_errors
                 conflict_errors = conflict_errors + 1
                 method_name = REQUEST.get('PATH_INFO', '')
-                err = ('ZODB conflict error at %s '
+                err = ('ZODB conflict error at %s: %s'
                        '(%s conflicts since startup at %s)')
-                LOG(err % (method_name, conflict_errors, startup_time),
+                LOG(err % (method_name, str(v), conflict_errors, startup_time),
                     INFO, '')
                 LOG('Conflict traceback', BLATHER, '', error=sys.exc_info())
                 raise ZPublisher.Retry(t, v, traceback)

Reply via email to