[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#4387) slapd-ldap backend leaks descriptors on closed connections on x86_64

Aleksander Adamowski wrote:
> On 2/5/06, Howard Chu <hyc@symas.com> wrote:
>> Explicit binds to the back-ldap database always use a new connection.
>> But if you Bind to a user in some other local database and then use that
>> identity when searching back-ldap, then a connection for that identity
>> will be cached. This behavior is already described in the 2nd paragraph
>> of the slapd-ldap(5) manpage. You should rework your configuration if
>> you want to take full advantage of the connection caching.
> Understood. Still, it doesn't justify slapd-ldap leaking unused
> connections to the target server.

Right, the leak needs to be fixed.

> And I think that theoretically, connection caching would be possible
> even with explicit binds to back-ldap.
> It would require some sort of an associative array (a mapping similar
> to: (bound identity) --> (connection)), with associations being
> changed upon each bind operation for each connection.

Associations are already changed upon completion of a Bind. But 
obviously you cannot be sharing a single connection across multiple 
clients when a Bind occurs, because any outstanding operations will be 
(and must be) invalidated.

  -- Howard Chu
  Chief Architect, Symas Corp.  http://www.symas.com
  Director, Highland Sun        http://highlandsun.com/hyc
  OpenLDAP Core Team            http://www.openldap.org/project/