From: Francis Cianfrocca <garbagecat10@...>
Date: 2006-05-17T07:00:22+09:00
Subject: Re: Ruby-LDAP and leftover connections

Sean, if you have evidence that you are leaking a connection (perhaps
from /proc/pid/fd), then you should consider the possibility that the
underlying native-LDAP library is leaking the connection, regardless
of Ruby's behavior. I'm quite sure (from experience) that this happens
with certain versions of the openldap client when you bind
unsuccessfully, and it happens even if you do the right thing and call
unbind (or have Ruby call it for you at the end of the block).

On 5/16/06, Sean Hussey <seanhussey@gmail.com> wrote:
> That bit about the block is a huge and powerful concept.  I learned
> about the general concept this weekend at the Rails studio and
> wondered if it applied to RubyLDAP.  Thanks for pre-answering my
> question!
>
> I think I'll try to rewrite pieces of the app to apply that method.
>
> Thanks!
>
> Sean
>
>
> On 5/15/06, Takaaki Tateishi <ttate@ttsky.net> wrote:
> > Sean Hussey wrote:
> > > I'm using RubyLDAP all over the place in my Rails app.  I'm curious,
> > > though, if I'm not specifically unbinding in certain places, are the
> > > connections kept open?
> >
> > The connection is kept open until the connection object is garbage collected, if you call
> > the binding method without a block. However, if you call the binding method with a block,
> > the connection is closed using Conn#unbind at the end of the block.
> >
> > Also, Ruby/LDAP wraps up the native LDAP library as Francis wrote. So behavior
> > of the binding and unbinding methods rely on C API called ldap_bind() and ldap_unbind()
> > defined in RFC1823. In particular, ldap_unbind() is defined to close the connection as follows.
> >    4.3.  Closing the connection
> >      ldap_unbind() is used to unbind from the directory and close the
> >      connection.
> >            int ldap_unbind( LDAP *ld );
> > --
> > Takaaki Tateishi <ttate@ttsky.net>
> >
> >
>
>