Hi all,
I asked this over on web-sig [1] earlier today, but am asking here
since it looks to only mod_wsgi related...
I've been trying to use the multiprocessing [2] w/ mod_wsgi and have
noticed what appears to be deadlocking behavior with body django and
web.py. I created a minimal example with web.py to demonstrate [3].
If you have mod_wsgi and web.py available, and and put something like
this in your apache config:
WSGIScriptAlias /multiprocessing /home/ed/wsgi_multiprocessing.py
AddType text/html .py
then visit:
http://localhost/
and compare with:
http://localhost/?multiprocessing=1
you should see the second URL hang.
Going forward I'm most likely going to move this functionality to an
asynchronous queue (celery, etc) but I was wondering if
multiprocessing + mod_wsgi was generally known to be something to
avoid, or if it was even forbidden somehow.
Any assistance you can provide would be welcome.
//Ed
[1] http://mail.python.org/pipermail/web-sig/2011-May/005065.html
[2] http://docs.python.org/library/multiprocessing.html
[3] https://gist.github.com/951570
--
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.
