Hi Andrew,

I was concerned about that too. I did try closing the connection before the
processes were spawned(in the verify_for_range method) but that didn't
solve the issue.

Regards,
Anuj


On Thu, Oct 24, 2013 at 7:49 PM, Andrew Melton <notifications@github.com>wrote:

> In verifier/base_verifier.py:
>
> >              with message_service.create_connection(
> >                  self.config.host(), self.config.port(),
> >                  self.config.userid(), self.config.password(),
> >                  "librabbitmq", self.config.virtual_host()) as conn:
> >                  def callback(result):
> > -                    (verified, exist) = result
> > -                    if verified:
> > -                        self.send_verified_notification(
> > -                            exist, conn, exchange, routing_keys=routing_keys)
> > -
> > +                    try:
> > +                        #Handle obscure mysql and Django multiprocessing bug
> > +                        #http://python.6.x6.nabble.com/Python-Multiprocessing-With-Django-td231840.html
> > +                        from django.db import connection
> > +                        connection.close()
>
> I wonder if this is really the best place to be closing the connection.
> With it here, the connection will get closed and reopened on each call
> back... When testing this out, did you attempt closing the connection at
> other locations. Perhaps closing it only once?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/rackerlabs/stacktach/pull/229/files#r7188937>
> .
>