You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mina.apache.org by "David Brooker (JIRA)" <ji...@apache.org> on 2017/02/23 20:44:44 UTC

[jira] [Updated] (FTPSERVER-424) Leak of allowed passive ports

     [ https://issues.apache.org/jira/browse/FTPSERVER-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Brooker updated FTPSERVER-424:
------------------------------------
    Attachment: FTPS_All-in-One_1MB_200VU_upload.jmx

JMeter Testplan that uses FTPS sampler (customized FTP Sampler that uses Apache FTPS client) to run up 200 threads, each uploading a 1MB file via Passive FTPS in Implicit mode. 

> 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
>         Attachments: FTPS_All-in-One_1MB_200VU_upload.jmx
>
>
> 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
(v6.3.15#6346)