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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0-M2
• Fix Version/s: 1.0.6, 1.1.0
• Component/s: Server
• Environment: Windows
• Assignee: Niklas Therning
• Reporter: Fred Moore
• Created: 14/Jan/09 16:51
• Updated: 18/Jun/11 21:41
• Resolved: 18/Jun/11 21:41

Description

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)?