From: Luis Lavena <luislavena@...>
Date: 2008-01-24T07:39:59+09:00
Subject: Re: Ruby on Windows with mysql and net

On 23 ene, 14:07, "Simon Jones" <n...@spam-required.foo> wrote:
> "Luis Lavena" <luislav...@gmail.com> wrote in message
>
> news:f1f18924-dc8e-46e7-9418-202c2b9e05a0@i7g2000prf.googlegroups.com...
>
> > On 23 ene, 10:31, "Simon Jones" <n...@spam-required.foo> wrote:
>
> > Just ignore the error for the time being? :-)
> > I'm doing that on a daily basis, so maybe you can too ;-)
>
> Thanks for that, Luis! I'm happy to ignore it now that I know there's
> nothing I can do about it:-)
>
> Have you noticed any unfortunate side effects from the issue? Any memory
> leaks or anything, either with the client code or at the MySQL end? Just
> curious to know if ignoring is going to catch up with me eventually!

In case you're using mongrel_service (for serving Rails applications)
you will find that sometimes the service fails at stopping process,
mostly due this.

libmysql.dll takes 2 or 3 seconds to release the locking on some
threads until it kill them. That isn't good, but so far, no data
corruption or any other issue server or client side besides the one I
mention from mongrel_service.

Regards,
--
Luis Lavena