Sorry this reply took so long, I am in the middle of changing jobs.
Anyway,
WSGIApplicationGroup %{GLOBAL}
does not change the rough frequency with which I see the problems. I
only added that directive for the port 80 virtual host, while the 443
virtual host doesn't have it. Should I add it to both?
Thanks,
Alex
On Apr 30, 1:47 am, Graham Dumpleton <graham.dumple...@gmail.com>
wrote:
> 2009/4/18 Alex Robbins <alexander.j.robb...@gmail.com>:
>
>
>
>
>
> >> When you say 'Also, I get no errors if I remove the maximum-requests',
> >> is that on all configurations?
> > Yes, that fixes it in all of the cases.
>
> >> When you run your tests, are requests always sequential? Ie., no
> >> concurrent requests.
> > No, the url checker is threaded, it normally runs 10 concurrent
> > threads, each making a urllib.open call, printing the status code if
> > not 200, then terminating.
>
> >> Does it make a difference if you specify:
>
> >> WSGIApplicationGroup %{GLOBAL}
>
> > Not sure, home sick today so I can't try it.
>
> >> Finally, what other third party C extension modules do you use besides
> >> GeoDjango? Ie., databases, etc. Do you use ctypes module?
>
> > We are using the mysql backend (mysqldb I think) and Pycrypto.
>
> > No ctypes, and we don't use GeoDjango
>
> > Also, those pages don't use any crypto, that is only for credit card
> > stuff or transaction submission.
>
> Any update on whether:
>
> WSGIApplicationGroup %{GLOBAL}
>
> made a difference or not?
>
> Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to modwsgi@googlegroups.com
To unsubscribe from this group, send email to
modwsgi+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en
-~----------~----~----~----~------~----~------~--~---
