[ https://issues.apache.org/jira/browse/FTPSERVER-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Brooker updated FTPSERVER-481: ------------------------------------ Description: When loading the FTP server with 200 users that are downloading files via FTPS in passive mode (implicit), the server eventually appears to run out of passive ports. FTPD log shows numerous instances of "cannot find an available passive port" (see txt attachment). While embedded, it appears the ftpd server also has a memory leak (separate heap dump available upon request - file is too large to attach) Can be reproduced using JMeter with the attached testplan/ftps plugin in roughly 35 minutes. was:When loading the FTP server with 200 users that are downloading files via FTPS in passive mode (implicit), the server eventually appears to run out of passive ports. FTPD log shows numerous instances of "cannot find an available passive port" (see txt attachment). While embedded, it appears the ftpd server also has a memory leak (separate heap dump available upon request - file is too large to attach) > Artificially running out of passive ports under load > ---------------------------------------------------- > > Key: FTPSERVER-481 > URL: https://issues.apache.org/jira/browse/FTPSERVER-481 > Project: FtpServer > Issue Type: Bug > Components: Core > Affects Versions: 1.1.0 > Environment: Windows 2008R2 virtual machine with 4GB RAM, 4 CPU > cores. Oracle Java 1.8.0_121. FTP server configured for 200 users and passive > mode ports specified between 3000-3600. > Reporter: David Brooker > Attachments: ftpd-full.xml, ftpd_pp_leak_snip.txt, heap.zip, > Jmeter_testplan.zip > > > When loading the FTP server with 200 users that are downloading files via > FTPS in passive mode (implicit), the server eventually appears to run out of > passive ports. FTPD log shows numerous instances of "cannot find an available > passive port" (see txt attachment). While embedded, it appears the ftpd > server also has a memory leak (separate heap dump available upon request - > file is too large to attach) > Can be reproduced using JMeter with the attached testplan/ftps plugin in > roughly 35 minutes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)