It ususally means someone has pressed the "stop" button in their browser before all the data for a request has been sent to the client. IOW, it means that a TCP connection has been closed prematurely. THis should really not result in this error to the console, but it does. I think we're trying to catch this exception for 2.4. - C Lucas Hofman wrote:
Now and then I see the following error on the terminal from which Zope was started (when running in debug mode):
2001-05-22T09:18:33 ERROR(200) ZServer uncaptured python exception, closing channel <FCGIChannel connected 127.0.0.1:4983 at 9fe5cc0> (socket.error:(32, 'Broken pipe') [/usr/share/Zope-2.3.2-linux2-x86/ZServer/medusa/asynchat.py|initiate_send|211] [/usr/share/Zope-2.3.2-linux2-x86/ZServer/medusa/asyncore.py|send|282])
Zope is activated by an Apache Server via en FCGI connection. Zope 2.3.2/CMF1.0.
Anybody knows what this is?
-- Lucas Hofman PGS Research work: +47 67514059 PO Box 354 fax: +47 67526640 N-1326 Lysaker, Norway home: +47 67581373
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )