So, If I want some shared data that is accessible to all the apache 
processes and threads, can I use Value of multiprocessing to store those 
variables and acquire and release locks on them accordingly? 

On Monday, May 2, 2011 at 7:07:02 PM UTC+5:30, Ed Summers wrote:
> 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 
>  I created a minimal example with to demonstrate [3]. 
> If you have mod_wsgi and available, and and put something like 
> this in your apache config: 
>     WSGIScriptAlias /multiprocessing /home/ed/ 
>     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] 
> [2] 
> [3]

You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to