Got it !
I edited this file :
Zope-2.9.0/lib/python/ZPublisher/Publish.py
and added a print line in the publish function, at the beginning of the first except block :
<code>
def publish(request, module_name, after_list, debug=0,...):
...
try:
request.processInputs()
request_get=request.get
response=request.response
...
except:
print "exception raised in the publish module, in function publish",
sys.exc_type,sys.exc_value
# DM: provide nicer error message for FTP
sm = None
if response is not None:
sm = getattr(response, "setMessage", None)
...
</code>
print "exception raised in the publish module, in function publish",sys.exc_type,sys.exc_value
</code>
And here is the exception that is raised:
exception raised in the publish module, in function publish
ZODB.POSException.ConflictError database conflict error (oid 0x09, class Products.Transience.Transience.Increaser, serial this txn started with 0x036b192256c66688 2007-01-23 16:34:20.337891, serial currently committed 0x036b19236a4be0ee 2007-01-23 16:35:
24.913219)
What happend ?
Y.Chaouche
> From times to times, apparently randomly, I have the following
> uncaught exception in the console :
>
> 2007-01-23 10:41:07 ERROR ZServer uncaptured python exception, closing
> channel <ZServer.HTTPServer.zhttp_channel connected 10.75.49.51:48177
> < http://10.75.49.51:48177> at 0x44562e6c channel#: 140 requests:>
> (socket.error:(104, 'Connection reset by peer')
> [/opt/python2.4.2/lib/python2.4/asynchat.py|initiate_send|219]
> [/opt/aef/Zope-
> 2.9.0/lib/python/ZServer/medusa/http_server.py|send|417]
> [/opt/python2.4.2/lib/python2.4/asyncore.py|send|332])
This means that when Zope was sending a response to the browser,
user pressed a 'Stop' button in browser, closed browser tab/window etc.
Nothing to worry about.
--
Maciej Wisniowski