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 POST.copy() like he did to fix it when I had the problem. Alex -- Alex Robbins 5Q Communications, Inc. http://www.5Qcommunications.com/ alex.robb...@5qcommunications.com 800-747-4214 ext 913 (p) http://www.ask5q.com/twitter/ On Mon, Apr 26, 2010 at 1:48 PM, Christoph Schindler <h...@30hopsmax.at> wrote: > 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. >> http://bitbucket.org/chris1610/satchmo/issue/951/mod_wsgi-thread-deadlocking-issue >> >> Maybe you are seeing a similar issue? > > You are my hero! > > hop > > -- > the pen is mightier than the pigs > > -- > You received this message because you are subscribed to the Google Groups > "Satchmo users" group. > To post to this group, send email to satchmo-us...@googlegroups.com. > To unsubscribe from this group, send email to > satchmo-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/satchmo-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to satchmo-us...@googlegroups.com. To unsubscribe from this group, send email to satchmo-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
