2010/1/22 Shachar Shemesh <[email protected]>: > Graham Dumpleton wrote: > > 2010/1/22 Shachar Shemesh <[email protected]>: > > > What version of mod_wsgi are you using? > > > 2.5-1~lenny1 > > If using mod_wsgi 3.1, try mod_wsgi 2.8 instead and tell us if it is > any different. > > > > I'm not sure it's going to be simple to upgrade to 2.8. If you know of a > problem, I'll give it a shot.
I only mentioned that for case where you were using mod_wsgi 3.1. You aren't. > Also try a simple WSGI hello world program that doesn't use a web > framework. See: > > http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide > > > > When the exact same script (the web2py gateway script) is run without an > AJAX data in the request, the problem does not happen. Only when there is > data on the GET request does the problem happen. Also, the problem does not > happen if we use the web2py "built in" server, only through Apache. > > for an example. > > Also try putting some print statements in WSGI script file and see if > the time isn't just the time taken to import web application the first > time. Thus add at start of WSGI script: > > > I have to confess that I did not perform the original installation, and it's > my first time with wsgi, so I'm not sure to what you refer as the WSGI > script. If it's the script that appears in the WSGIAlias line in the Apache > config, then I've already tried placing a print at the beginning and end. > The script is called about four seconds after the request arrives, completes > almost immediately, and then there are about six more seconds of delay > before the answer is returned to the browser. If the delays are before the import, not going to be mod_wsgi itself. > Also, if immediately after the problem happens you perform another > operation, that completes fairly quickly (about a second). If, however, you > wait about 30 or 50 seconds, the problem happens again. In part almost sounds like your Apache configuration has too few process/threads for Apache server child process and you are tying them all up because of having keep alive enabled with some ridiculous value. This would cause a delay in subsequent requests as no threads for Apache to accept connection. Try disabling keep alive in Apache server and see if it makes a difference. KeepAlive Off Problem could also be caused by you returning wrong content length for response. This may interact with keep alive and lack of threads to handle requests to cause it. Graham -- 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.
