[Zope] Z2 CONFLICT & ZServer uncaptured python exception

Dieter Maurer dieter@handshake.de
Fri, 8 Mar 2002 21:05:21 +0100


Marcus Schopen writes:
 > find this many time in z2.log:
 > 
 > 2002-03-07T14:29:20 INFO(0) Z2 CONFLICT Competing writes at, /index.html
 > Traceback (innermost last):
 >   File /home/zope/Zope/lib/python/ZPublisher/Publish.py, line 175, in
 > publish
 >   File /home/zope/Zope/lib/python/Zope/__init__.py, line 235, in commit
 >   File /home/zope/Zope/lib/python/ZODB/Transaction.py, line 300, in
 > commit
 >   File /home/zope/Zope/lib/python/ZODB/Connection.py, line 281, in
 > commit
 > ConflictError: '\000\000\000\000\000\000\212\032'
Apparently, this "index.html" is often rewritten.

Usually, this is not intended.

 > ------
 > 2002-03-07T17:44:27 ERROR(200) ZServer uncaptured python exception,
 > closing channel <FCGIChannel connected at 87606e8> (socket.error:(32,
 > 'Broken pipe')
 > [/home/zope/Zope-2.3.0-linux2-x86/ZServer/medusa/asynchat.py|initiate_send|211]
 > [/home/zope/Zope-2.3.0-linux2-x86/ZServer/medusa/asyncore.py|send|282])
That's harmless: the user was not patient and either pressed the
"stop" button in his browser or started a new request before the old
were finished.


Dieter