Yes, Thank you. That is the case.
In the (short while) i was waiting for a response, :)
I was looking at mules, would this a better solution ?
On 3/19/13 8:43 AM, Roberto De Ioris wrote:
Hey There,
Nice work with 1.9!
I have a Flask app running ApScheduler to do some job scheduling.
When I run the app using uwsgi, I use the ednable-threads flag as
ApScheduler needs Threading support.
It seems when the app starts up and Jobs scheduled get run, so I guess
that means that the threading support works as intended
However, if I continue to add more jobs to the Scheduler, then those
jobs never get run.
Is there some other flag I should be setting??
I am using v1.9
Thanks in advance for any advice.
--enable-threads is enough to have a consistent python threading support.
From what you describe it looks like you are loading your app in the master
(spawning the first thread) but then you add tasks from the workers (where
the thread no more exists).
If it is the case just add --lazy-apps to load the app one time per worker.
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
