On 11.03.2011 15:39, Graham Dumpleton wrote: > On 10 March 2011 03:13, Thomas Guettler <[email protected]> wrote: >> Hi, >> >> From time to time one URL hangs, in my python code, since >> an other system is not available (not the fault of mod_wsgi). >> >> But this hanging page/url "eats" all request handlers. Sooner or later >> all request handlers wait for this hanging url. Other wsgi-application >> still work fine. >> >> My config: >> >> WSGIDaemonProcess modwork_foo_p user=modwork_foo_p group=modwork_foo_p >> threads=1 processes=8 maximum-requests=100 >> WSGIScriptAlias /modwork >> /home/modwork_foo_p/modwork_foo/apache/django_wsgi.py >> <Location "/modwork"> >> WSGIProcessGroup modwork_foo_p >> WSGIApplicationGroup %{GLOBAL} >> WSGIReloadMechanism Process >> </Location> >> >> What can I do to avoid this? >> >> If the timeout is set to e.g. 60 seconds, some other pages won't work, since >> they need longer. > > Which timeout are you talking about?
I talked about the Apache Timeout: http://httpd.apache.org/docs/2.2/mod/core.html#timeout Thank you very much for the detailed answer. I will handle the blocking operation in my code: I will use locking to ensure that only N processes (with N much smaller than wsgi-processes) access the possible blocking code. If the code blocks, and there are more than N http-requests, they will get a "try again later" response from my code. Thomas -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de -- 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.
