2009/12/22 TheDeadOne <[email protected]>: >> >> That doesn't answer any of the questions I asked. :-( >> >> Graham >> >> > > Problem was with apache. It was build with no thread support.
If you have solved the issue then fine, but there should be no issue in respect of whether Apache itself is compiled for threaded versus non threaded MPM, ie., worker vs prefork MPM. On the other hand, if the underlying Apache run time libraries have not been compiled with threading awareness then there would, but your messages indicate that Apache was at least running. If APR was not compiled with threading then mod_wsgi probably wouldn't even load and Apache would fail to start, so lack of threading in APR can't be the issue either as you were indicating that you were getting an error when a request was being handled. So, you obviously had something wrong in your setup, but what it was is still debatable as insufficient information to tell. Graham > 1. I didn't understand question. What actually did you want to know? > Httd.conf file content? > 2. Something like http://10.18.4.245/mysite/test. I'm use mod_wsgi > with Django. > 3. No. > 4. Yes. > 5. My OS is FreeBSD. > 6. No, I tried Django. > > -- > > 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. > > > -- 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.
