One more additional info: both virtual host configs have one WSGIAliasScript directive mounting different wsgi scripts on the the same relative url. ( which shouldn't be a problem because it's for different virtual hosts )
On Jan 24, 1:35 pm, JE <[email protected]> wrote: > Hi ! > > I have got a quick question. We have started running two different > virtual hosts on the same server, and thought that we can have them > both run in the same WSGIDaemonProcess group. It seems that it doesn't > work as expected - because there are some mixup happening as requests > are processed. We are trying to figure out if the cause is our > mod_wsgi config or may be our python modules itself. > > While reading through the documentation of mod_wsgi we found that the > description of WSGIDaemonProcess seems to have contradicting > statements: > [...] > Note that the name of the daemon process group must be unique for the > whole server. **That is, it is not possible to use the same daemon > process group name in different virtual hosts.** > [...] > If **the WSGIDaemonProcess directive is specified outside of all > virtual host containers**, any WSGI application can be delegated to be > run within that daemon process group. > [...] > > So my question is can we have a WSGIDaemonProcess directive with the > same name for different virtual hosts, by putting it into the server > config? > Additional info: the applicationgroup is %{GLOBAL}% and we have > multiple processes. > > Thank you in advance, > Jan-Eric -- 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.
