> > > Very quickly on one point as is late. > > You want to override --request-timeout option. This defaults to 60 > seconds. Even if you only had one request, with 5 threads the WSGI process > will be force restarted after 300 seconds. If you don't want a timeout try > --request-timeout 0. That way requests can run as long as they like and is > what straight Apache/mod_wsgi behaves like. > > OK - I will try as soon as I can (its the long summer "bank holiday" weekend here in the UK so i might not be allowed anywhere near a computer!).
With apache "extra.conf" settings still set to Timeout 21600 RequestReadTimeout header=300-360,MinRate=500 body=300-360,MinRate=500 LogLevel info and mod_wsgi-express set to --include extra.conf # hmm shouldn't that be --include-file but it appears to work --socket-timeout 3600 --request-timeout 60 --debug-mode I ran a test data request for 85 minutes before it fell over with another (unrelated and stupid) python exception that I have now fixed. I am repeating that run to make sure this aspect is out of the equation. Dave -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
