Ahem. I overlooked /etc/httpd/conf.d/swtune.conf which contains MPM parameters evaluated after the parameters in httpd.conf. In swtune.conf, I changed this
<IfModule worker.c> StartServers 1 MaxClients 10 MinSpareThreads 1 MaxSpareThreads 4 ThreadsPerChild 25 MaxRequestsPerChild 0 </IfModule> to this <IfModule worker.c> StartServers 1 MaxClients 9 MinSpareThreads 3 MaxSpareThreads 9 ThreadsPerChild 3 MaxRequestsPerChild 0 </IfModule> and Apache starts with worker MPM and mod_wsgi. Now I have a working configuration for three apps set up like this: WSGIDaemonProcess djangolit user=apache group=apache threads=10 stack- size=524288 maximum-requests=3000 deadlock-timeout=30 inactivity- timeout=100 WSGIProcessGroup djangolit Unfortunately, there are even more QoS alerts than before (with prefork MPM). How do the process/thread related directives of the Apache configuration to the process/thread related option of WSGIDaemonProcess? Kind regards, Jan -- 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.
