Our current project uses two Django applications - a third party forum application, and a Django app we're developing ourselves that encloses the forum app, so to speak. Both applications need to appear at the same host/port/etc.
The trouble is that, almost completely at random, requests to the forum app return a 404 from the OTHER application. We have never observed this working the other way, which may be because the enclosing application is always the first to be run. If the user refreshes the page when a 404 shows up, there is a chance (about 50% or so) that it will return to the forum page. We are using Apache with mod_python, and no VirtualHosts. Rather, because the URL spaces for the two apps are non-overlapping, we just direct each Location to the proper application. The forum app uses a different PythonInterpreter than the other app, and the settings file is different for each app. We have recently switched to the worker MPM. We know that while Django says to use prefork, we've heard from others that worker works fine in most cases, and due to the high-volume Ajax nature of our application, worker is the only way we've found to prevent our server from being overrun during peak use times. However, because worker is the big thing that has changed recently, and the problem was not observed before then, it seems a likely suspect. Other observations: once the problem has been observed, if httpd is restarted, there is a good chance everything will be fine for a certain period. If the problem is not observed, restarting httpd can cause the behavior to start up again. However - it only seems to happen if 20 or more users are logged in at once, sending AJAX calls. The randomness suggests to me that some number of httpd.worker processes has a chance at somehow being corrupted, or caching calls to the wrong PythonInterpreter. However, if this is so, I'm not really sure how to repair or workaround the issue. Thanks for any insight! Chris Guin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
