Thanks Jirka, that fixed the problem. But I think I will file a bug report that seem to be very hacky :)
Vitaly Babiy On Fri, Mar 6, 2009 at 11:15 AM, Vitaly Babiy <vbabi...@gmail.com> wrote: > Alright I will have to give this a try > > Vitaly Babiy > > > > On Fri, Mar 6, 2009 at 10:30 AM, Jirka Vejrazka > <jirka.vejra...@gmail.com>wrote: > >> >> > I have a management command that that starts up a few process to process >> a >> > request: http://dpaste.com/7925/. >> >> Hi, I was recently debugging similar issue and came to a conclusion >> (which may be wrong of course :) that multiprocessing and Django DB >> connections don't play well together. I ended up closing Django DB >> connection first thing in the new process. It'll recreate a new >> connection when it needs one, but that one will have no references to >> the connection used by the parent. >> >> So, my Process.start() calls a function which starts with: >> >>> from django.db import connection >> >>> connection.close() >> >> This solved my problem. >> >> Cheers >> >> Jirka >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
