hello everyone,
I'm testing webpy app using apachebench, and I found a serious problem
that when a number of clients disconnect intentionally it will
deadlock.. While using flup directly I will not encounter this
problem, im wondering if this problem exists in dhango.
I set up two groups of testing environments. One is flup + nginx +
fastcgi and the other one is webpy + nginx + fastcgi, the versions
respectively are webpy 0.34 stable, newest flup and nginx 0.8.22.
When use apachebench and send more than 100 requestsin parallel, if it
goes well till the end of the test, it is no problem.
The problem appear when the apachebench is killed before the end of
this test, webpy will die, when debugging , found all process the flup
open are normal acquiring the lock, so lock dies, reasons unknown.
If test by using flup directly, then there’s no such a problem, so
webpy is free from responsibility.
here are the testing code:
webpy:
import web
class index:
def GET(self):
return 'ok'
app = web.application(('/', index))
app.run()
flup:
from flup.server.fcgi import WSGIServer
def app(environ, start_response):
start_response('200 OK', [('Content-Type', 'text/html')])
yield 'ok'
WSGIServer(app, bindAddress=('localhost', 9589)).run()
Has this problem ever occurred to you?
Regards,
Cat.
--
You received this message because you are subscribed to the Google Groups
"web.py" 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/webpy?hl=en.
