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

Posted to dev@mina.apache.org by "Niklas Gustavsson (JIRA)" <ji...@apache.org> on 2011/06/18 23:41:47 UTC

[jira] [Closed] (FTPSERVER-264) It takes about 1 minute and 100% CPU to set a "wide" passive port range (org.apache.ftpserver.DefaultDataConnectionConfiguration$Passive.SetPorts())

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

Niklas Gustavsson closed FTPSERVER-264.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.6

Fixed in rev 1137251 and 1137252.

> 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
>            Assignee: Niklas Gustavsson
>             Fix For: 1.0.6, 1.1.0
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira