[
https://issues.apache.org/jira/browse/FTPSERVER-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fred Moore updated FTPSERVER-264:
---------------------------------
Summary: It takes about 1 minute and 100% CPU to set a "wide" passive port
range
(org.apache.ftpserver.DefaultDataConnectionConfiguration$Passive.SetPorts())
(was: It takes about 1 minute and 100% CPU to set a "wide" the passive port
range
(org.apache.ftpserver.DefaultDataConnectionConfiguration$Passive.SetPorts()))
> It takes about 1 minute and 100% CPU to set a "wide" passive port range
> (org.apache.ftpserver.DefaultDataConnectionConfiguration$Passive.SetPorts())
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FTPSERVER-264
> URL: https://issues.apache.org/jira/browse/FTPSERVER-264
> Project: FtpServer
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.0.0-M2
> Environment: Windows
> Reporter: Fred Moore
>
> We observed a long (about 1 minute) plateau of 100% CPU when trying to
> setPorts() in org.apache.ftpserver.DefaultDataConnectionConfiguration$Passive
> with "wide" port ranges such as 2122-65535.
> We observed that FTPServer internally performs an apparently very expensive
> scan on this range.
> Can this be made less CPU intensive and quicker (to shorten server downtime
> and reduce resource consumption in production)?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
