[jira] Commented: (FTPSERVER-177) Passive port ranges are not properly released

["Kevin Conaway (JIRA)" <ji...@apache.org>]

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

Kevin Conaway commented on FTPSERVER-177:
-----------------------------------------

We haven't noticed it but our use cases are very simple and we're not using any commands other than STOR or QUIT

Thanks for your quick response.

> Passive port ranges are not properly released
> ---------------------------------------------
>
>                 Key: FTPSERVER-177
>                 URL: https://issues.apache.org/jira/browse/FTPSERVER-177
>             Project: FtpServer
>          Issue Type: Bug
>    Affects Versions: 1.0
>            Reporter: Kevin Conaway
>            Assignee: Niklas Gustavsson
>            Priority: Critical
>             Fix For: 1.0-M4
>
>         Attachments: FTPSERVER-177.patch
>
>
> When using a range of passive ports, the passive ports are not appropriately released.  This leads to a deadlock after all the ports in the range have been filled up.
> I believe that this is because the QUIT command should be calling session.getDataConnection().closeDataConnection(); which in turn calls session.getListener().getDataConnectionConfiguration().releasePassivePort(<portNumber>);
> In the attached patch, I've modified the org.apache.ftpserver.clienttests.PasvTest testcase to use a 1-value range of passive ports which exposes this issue.  I've also added the session.getDataConnection().closeDataConnection() to the QUIT command

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.