[
https://issues.apache.org/jira/browse/FTPSERVER-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964001#comment-15964001
]
Aymeric Caroff commented on FTPSERVER-424:
------------------------------------------
Just to add my 2 cents:
In IODataConnectionFactory, line 226, I see this:
{code}
servSoc = null;
closeDataConnection();
{code}
which seems wrong considering closeDataConnection() is checking if servSoc is
null before invoking close() - so close will never be invoked.
Removing the 1st line (servSoc = null) should fix the (or at least part of the)
problem.
> 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)
