This have been already checked, no time_wait ... I have read that closing explicitly the handle could be necessary after closing socket on Windows (yes a bug)
-----Message d'origine----- De : Niklas Gustavsson [mailto:[EMAIL PROTECTED] Envoyé : mardi 6 mai 2008 16:28 À : [email protected] Objet : Re: So many handles for Server in windows ? On Tue, May 6, 2008 at 4:00 PM, Gerard Frederic <[EMAIL PROTECTED]> wrote: > I have observed these handles are bound to sockets creation: > they are created at the same time as the new sockets (all are green or red > in process explorer) > all sockets are relesed at the end, but all \Dev\Afd\Endpoint remain > so if i transfer 100 files, there will be about 100 endpoints at the end Okay, have you confirmed that the socket has actually been closed and is not i TIME_WAIT waiting to be closed? You can find out by running netstat -a and see if you got a similar amount of sockets in TIME_WAIT. > The same server library is ok on linux, everything is cleaned That might indicate that this is not an issue with FtpServer. /niklas Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
