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

Posted to dev@mina.apache.org by "Mark Riordan (JIRA)" <ji...@apache.org> on 2017/04/11 00:16:41 UTC

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

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

Mark Riordan commented on FTPSERVER-424:
----------------------------------------

My colleague Harry Gu has diagnosed and fixed this leak in the free list.  Expect a one-line patch here within a few days.  

> 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: ApacheJMeter_addons.jar, FTPS_All-in-One_1MB_200VU_upload.jmx, MINA_Config.zip, MINA_FTP_Error.txt, Snapshots.zip
>
>
> 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)