Twisted Web wsgi container often calls Request.finish after connection is closed

New submission from exarkun <[email protected]>:

This results in an unhandled exception:

{{{
2009-09-14 15:28:38-0400 [-] Unhandled Error
        Traceback (most recent call last):
          File "/srv/trac/.local/lib/python2.5/site-packages/twisted/application/app.py", line 445, in startReactor
            self.config, oldstdout, oldstderr, self.profiler, reactor)
          File "/srv/trac/.local/lib/python2.5/site-packages/twisted/application/app.py", line 348, in runReactorWithLogging
            reactor.run()
          File "/srv/trac/.local/lib/python2.5/site-packages/twisted/internet/base.py", line 1166, in run
            self.mainLoop()
          File "/srv/trac/.local/lib/python2.5/site-packages/twisted/internet/base.py", line 1175, in mainLoop
            self.runUntilCurrent()
        --- <exception caught here> ---
          File "/srv/trac/.local/lib/python2.5/site-packages/twisted/internet/base.py", line 752, in runUntilCurrent
            f(*a, **kw)
          File "/srv/trac/.local/lib/python2.5/site-packages/twisted/web/wsgi.py", line 299, in wsgiFinish
            self.request.finish()
          File "/srv/trac/.local/lib/python2.5/site-packages/twisted/web/http.py", line 828, in finish
            "Request.finish called on a request after its connection was lost; "
        exceptions.RuntimeError: Request.finish called on a request after its connection was lost; use Request.notifyFinish to keep track of this.
}}}


----------
Type     : defect
Component: web
Keywords : 
Priority : normal
Nosy     : 
----------
http://twistedmatrix.com/trac/ticket/4025