Interesting news about this issue... FtpServer uses intrinsically many localhost tcp connections on Windows, not on Linux Maybe Java 5 use different implementations of the same methods on theses OS And these connections end with time_wait state
Here is a netstat result, all the time_wait sockets come from FtpServer, and only on Windows ! TCP 127.0.0.1:1068 0.0.0.0:0 LISTENING TCP 127.0.0.1:1621 127.0.0.1:1622 ESTABLISHED TCP 127.0.0.1:1622 127.0.0.1:1621 ESTABLISHED TCP 127.0.0.1:1623 127.0.0.1:1624 ESTABLISHED TCP 127.0.0.1:1624 127.0.0.1:1623 ESTABLISHED TCP 127.0.0.1:3187 127.0.0.1:9930 ESTABLISHED TCP 127.0.0.1:3190 127.0.0.1:3191 ESTABLISHED TCP 127.0.0.1:3191 127.0.0.1:3190 ESTABLISHED TCP 127.0.0.1:3325 127.0.0.1:3326 TIME_WAIT TCP 127.0.0.1:3329 127.0.0.1:3330 TIME_WAIT TCP 127.0.0.1:3339 127.0.0.1:3340 TIME_WAIT TCP 127.0.0.1:3341 127.0.0.1:3342 TIME_WAIT TCP 127.0.0.1:3343 127.0.0.1:3344 TIME_WAIT TCP 127.0.0.1:3345 127.0.0.1:3346 TIME_WAIT TCP 127.0.0.1:3347 127.0.0.1:3348 TIME_WAIT TCP 127.0.0.1:3349 127.0.0.1:3350 TIME_WAIT TCP 127.0.0.1:3353 127.0.0.1:3354 TIME_WAIT TCP 127.0.0.1:3355 127.0.0.1:3356 TIME_WAIT TCP 127.0.0.1:3357 127.0.0.1:3358 TIME_WAIT TCP 127.0.0.1:3359 127.0.0.1:3360 TIME_WAIT TCP 127.0.0.1:3361 127.0.0.1:3362 TIME_WAIT TCP 127.0.0.1:3367 127.0.0.1:3368 TIME_WAIT TCP 127.0.0.1:3369 127.0.0.1:3370 TIME_WAIT TCP 127.0.0.1:3371 127.0.0.1:3372 TIME_WAIT TCP 127.0.0.1:3379 127.0.0.1:3380 TIME_WAIT TCP 127.0.0.1:3381 127.0.0.1:3382 TIME_WAIT TCP 127.0.0.1:3387 127.0.0.1:3388 TIME_WAIT TCP 127.0.0.1:3390 127.0.0.1:3391 TIME_WAIT TCP 127.0.0.1:3398 127.0.0.1:3399 TIME_WAIT TCP 127.0.0.1:3402 127.0.0.1:3403 TIME_WAIT TCP 127.0.0.1:3404 127.0.0.1:3405 TIME_WAIT TCP 127.0.0.1:3406 127.0.0.1:3407 TIME_WAIT TCP 127.0.0.1:3408 127.0.0.1:3409 TIME_WAIT TCP 127.0.0.1:3416 127.0.0.1:3417 TIME_WAIT TCP 127.0.0.1:3418 127.0.0.1:3419 TIME_WAIT TCP 127.0.0.1:3426 127.0.0.1:3427 TIME_WAIT TCP 127.0.0.1:3428 127.0.0.1:3429 TIME_WAIT TCP 127.0.0.1:3430 127.0.0.1:3431 TIME_WAIT TCP 127.0.0.1:3434 127.0.0.1:3435 TIME_WAIT TCP 127.0.0.1:3436 127.0.0.1:3437 TIME_WAIT TCP 127.0.0.1:3440 127.0.0.1:3441 TIME_WAIT TCP 127.0.0.1:3452 127.0.0.1:3453 TIME_WAIT TCP 127.0.0.1:3454 127.0.0.1:3455 ESTABLISHED TCP 127.0.0.1:3455 127.0.0.1:3454 ESTABLISHED TCP 127.0.0.1:9930 127.0.0.1:3187 ESTABLISHED UDP 127.0.0.1:123 *:* UDP 127.0.0.1:1028 *:* UDP 127.0.0.1:1044 *:* UDP 127.0.0.1:1056 *:* UDP 127.0.0.1:1149 *:* UDP 127.0.0.1:1266 *:* UDP 127.0.0.1:1900 *:* UDP 127.0.0.1:2233 *:* UDP 127.0.0.1:3654 *:* UDP 127.0.0.1:4162 *:* Frédéric -----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.
