Graham, thanks for the information!
I know very, very little about mod_wsgi, but would it be possible to
pull the request content out of the socket and store it somewhere else
every time? It seems like the bug only gets us when we don't do
something with all the request data. Why not
I had an error like this one time. It was due to mod_wsgi being
unhappy if data was posted but the POST dict wasn't ever accessed. The
five minutes is the timeout on your socket.
http://bitbucket.org/chris1610/satchmo/issue/951/mod_wsgi-thread-deadlocking-issue
Maybe you are seeing a similar
On Mon, Apr 26, 2010 at 12:52:58PM -0500, Alex Robbins wrote:
I had an error like this one time. It was due to mod_wsgi being
unhappy if data was posted but the POST dict wasn't ever accessed. The
five minutes is the timeout on your socket.
I wonder if this is something that should/could be handled in django's
wsgi.py mod_wsgi handler? I don't really know who to blame for the
problem, django or mod_wsgi, or someone else?
Anyway, it probably be good to file a bug report for the view you are
seeing this on, so Chris can add a useless
