Re: (ITS#4585) slapd-search generates TIME_WAIT connections increasingly

[Kurt@OpenLDAP.org]

First, TIME_WAITs are normal in the processing of TCP.
Upon both sides acknowledging being finished (FIN/ACK, ACK),
each waits an amount of time before moving to the CLOSED
state.

Second, CLOSE_WAITs indicate the peer has indicated
its finished (FIN/ACK) but the program has not yet
indicated its finished.

You should enable some client logging or otherwise
determine whether the library is attempting to close
the socket and, if so, whether it called shutdown(2).

-- Kurt

At 11:43 PM 6/11/2006, roland_scholz@securecomputing.com wrote:
>Full_Name: Roland Scholz
>Version: 2.3.24
>OS: Solaris 9
>URL: ftp://ftp.openldap.org/incoming/
>Submission from: (NULL) (80.66.20.180)
>
>
>If I use the test program sladp-search to connect to a Microsoft Active
>Directory 10000 times (with -l 10000), the number of connections in TIME_WAIT
>state increase steadily. This does not happen if I use a OpenLDAP server
>instead. To reproduce, you just need a Microsoft Active Directory server and use
>slapd-search with parameter -l 10000 (or higher).
>I submit this bug report, because I came accross this problem when I tried to
>reproduce  a problem we face when we use OpenLDAP library with our application.
>With our application we can observe the number of connections in CLOSE_WAIT
>state increasing, if Microsoft Active Directory server is used. This is
>critical, because the CLOSE_WAITS are increasing until no new connection can be
>opened.
>I assume that both problems are related.