On Fri, Oct 14, 2011 at 10:35 PM, Roberto De Ioris <[email protected]> wrote:
>
>> Unfortunately the issue persists, albeit at a lesser scale. Spooler
>> jobs were successfully created this morning and the workers don't
>> appear to be dying off quite as often. The config is the same as I
>> had posted before minus the max-requests and optimize flags. Here are
>> two excerpts from the logs:
>>
>>
>
> Ok, this confirm an issue with max-requests and the spooler (propagating
> to workers).
>
> Your latest errors seems triggered by the signal handling subsystem.
> I do not know if you need to spawn threads in your app, but if you do not
> need it, please disable --enable-threads to see if the signal-handler
> crash is triggered by a broken GIL lock.
Unfortunately I am currently using the enable-threads option to send
out emails. It looks something like this:
queues = {}
class queueconsumer(object):
def __init__(self, name, num=1, **kwargs):
self.name = name
self.num = num
self.queue = Queue.Queue()
self.threads = []
self.func = None
queues[self.name] = self
@staticmethod
def consumer(self):
while True:
req = self.queue.get()
self.func(req)
self.queue.task_done()
def __call__(self, f):
self.func = f
for i in range(self.num):
t = Thread(target=self.consumer, args=(self,))
self.threads.append(t)
t.daemon = True
t.start()
@queueconsumer('email', 2)
def send_email_task(args):
from django.core.mail import EmailMultiAlternatives
from django.utils import simplejson
body = args['body']
email_details = simplejson.loads(body)
email = EmailMultiAlternatives(**email_details)
email.send(fail_silently=False)
It's basically taken from the examples you guys posted a while ago for
multi-threaded spool jobs, but I don't create a spool job in this
situation, I just queue the email to be sent into the dictionary and
let the threads take care of it. I can re-work the code if you guys
would like me to see if this is causing the issue or not.
Also, I spoke too soon when I said that spooler jobs were being
created again, after being left running long enough, the spooler
system shut down and no longer created spool jobs or executed spool
jobs that had been left in it's spool.
Thanks for all the help on this,
Ryan-
>
> Many Thanks
>
> --
> Roberto De Ioris
> http://unbit.it
> _______________________________________________
> uWSGI mailing list
> [email protected]
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
