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

RE: Idletimeout value broken (ITS#2374)

My tests shows that the idletimeout works, though it may not work as you
expect. When there is no network activity at all, no checks of any kind are
performed. The idletimeout check is only performed when the service loop that
reads the descriptors has been wakened up by any activity. As such, if your
long idle connection is the only connection to slapd, it will stay open
forever. If you come in with another connection (search, whatever) while the
idle connection is open, it will be detected and closed. You can verify this
behavior using netstat.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: owner-openldap-bugs@OpenLDAP.org
> [mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of quanah@stanford.edu

> Full_Name: Quanah Gibson-Mount
> Version: 2.1.14
> OS: Solaris 8
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (
> Hello,
> As far as I can tell, the idletimeout flag in slapd.conf does
> nothing whatsoever
> for the server in causing idle connections to close.  We set
> idletimeout to be
> 30 on our machines, yet connections that are made, perform a
> single search, and
> then do not unbind, are allowed to remain connected for hours
> at a time.  A
> recent test we were doing of writing data to our directory
> server came up with
> the same result.  If you make a write, and then do not close
> the connection, it
> stays open for long periods of time, until the writing
> program itself recycled
> the connection.  These times could be well over 30 seconds
> (the highest was 86
> before the program in charge of writing closed the connection).