On Tue, Jun 28, 2011 at 2:53 AM, Anton Pirker <an...@ignaz.at> wrote: > Ah! There is a queue consumer daemon! ;) Thank's for this hint!
just checked and the @async decorator doesn't use the queue/consumer facility also included. sorry for the wrong hint. what @async does is adding to a python-standard Queue object, and also spawining one or more threads to consume the queue (so no need for a daemon). another thing I don't know about is gunicorn; but the 'g' in the name comes from 'green threads'. do you (or anybody else) know if that means that it patches the python thread implementation? if so, that could be interfering with the @async thread. OTOH, now that you have the daemon running, maybe it would be easier to use the djutils task queue. try changing the @async with @queue_command (found in djutils.queue.decorators) -- Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
