What version of mod_wsgi are you using? Are you returning response in good WSGI style, ie., returning iterable, or are you using the write() callback returned by start_response()?
Graham On 6 April 2011 23:16, Pedro Ferreira <[email protected]> wrote: > Dear all, > > I recently switched from mod_python to mod_wsgi (daemon mode) in a web > app that uses a lot of AJAX calls. From then on, I started getting > many IOErrors in the log, with the message "failed to write data". > From what I understood from everything I found while googling it, this > is normal in such context. > However, my log files are spammed with all those messages, and I'd > really like to get rid of them. I thought of just ignoring the > exception, which seems to be OK as I would just wrap a try...except > around the code that calls `start_response` and catch IOError > (right?)... or are there any other situations in which there can be an > IOError that I don't want to ignore? > Any suggestions? > > Thanks in advance, > > Pedro Ferreira > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
