On Nov 25, 6:43 pm, Crispin Wellington <cwelling...@ccg.murdoch.edu.au> wrote: > On Tue, 2009-11-24 at 21:52 -0800, Graham Dumpleton wrote: > > Your imagination is running amuck, no such thing happens. You can > > quite happily run multiple Django instances in embedded mode, they > > just need to be separated into distinct Python sub interpreters, which > > is the default behaviour of mod_wsgi. So, unless you have played with > > WSGIApplicationGroup to override the default, there should be an > > issue. > > We run multiple Django apps through mod_wsgi, have not touched > WSGIApplicationGroup, and we see these applications occasionally shift > environment contexts under load. We know this because we get tracebacks > emailed to us from one application, with the environment and Django > settings of another application. Each application has its own .wsgi file > in its own directory running its own virtual python. We use > WSGIScriptAlias to map a URI path to the wsgi file. The wsgi file sets > up the virtualpython using site.addsitedir(). The wsgi file sets the > DJANGO_SETTINGS_MODULE to point to the applications settings file. When > we run mod_wsgi in daemon mode, the problems go away.
I cant find your name against any posts to suggest that you have ever reported this on the mod_wsgi mailing list, or if you have you cant have hung around to help resolve it as this is something which would have been investigated quite thoroughly to get to the bottom of it. The closest similar problem can remember is people with badly configured Apache such that they had duplicate or overlapping VirtualHost configurations and Apache was executing requests in context of wrong VirtualHost in some cases. They fixed up their Apache configurations and all was fine. Most obvious case is people not setting NameVirtualHost properly and the other as mentioned is people fiddling with WSGIApplicationGroup. At the moment there is only a suggestion of an issue. No details on what version of mod_wsgi being used at the time or anything else in the way of detail. Not much to go on. One of the things that is most annoying about developing mod_wsgi is people asking about or saying they have a problem, usually with insufficient details, and you asking for more information, giving answers or suggestions about how to investigate and those people then never actually bother to come back and tell you what you need to know, what they found and whether or how they fixed or worked around the problem. You thus never know if there was a problem to be fixed or not. For Django related stuff, a lot of the time you don't even get that as people instead go off to #django IRC channel rather than bringing the issue to the mod_wsgi mailing list where it belongs. Sometimes I only find out about potential issues by trolling the #django IRC logs after the fact and even then you can only speculate whether it was a real issue or not. Perhaps next time you will consider reporting the problem to the mod_wsgi mailing list and helping to fully investigate it and help determine if there is a problem in mod_wsgi or not. At the moment there isn't believed to be any issues which would cause this. Graham -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
