mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Vigeant (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FTPSERVER-424) Leak of allowed passive ports
Date Thu, 31 Mar 2016 15:03:25 GMT

    [ https://issues.apache.org/jira/browse/FTPSERVER-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219991#comment-15219991

Eric Vigeant commented on FTPSERVER-424:

There is another leak of passive ports in IODataConnectionFactory.initPassivePortConnection()
line 166.

On line 166, the port is actually reserved, but will not get released if there is an error
establishing the serversocket because closeDataConnection checks if serverSocket != null before
releasing the port.

We have clients where the passive ports are exhausted very quickly because of this.

> Leak of allowed passive ports
> -----------------------------
>                 Key: FTPSERVER-424
>                 URL: https://issues.apache.org/jira/browse/FTPSERVER-424
>             Project: FtpServer
>          Issue Type: Bug
>    Affects Versions: 1.0.6
>            Reporter: Taras Puchko
> In several hours after start the server cannot accept passive connections if allowed
passive ports are configured.
> This is caused by FTPSERVER-420, org.apache.ftpserver.impl.PassivePorts.reserveNextPort()
lines 218-219,
> where the value removed from the freeList might be different from the value added to
the usedList, if checkPortUnbound returns false before.

This message was sent by Atlassian JIRA

View raw message