[FTPSERVER-197] start() and stop() methods in FtpServer class can fail to unbind ports.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0-M1, 1.0.0-M2, 1.0.0-M3
• Fix Version/s: 1.0.0-M4
• Assignee: Niklas Therning
• Reporter: David Latorre
• Created: 16/Oct/08 15:14
• Updated: 18/Oct/08 20:39
• Resolved: 18/Oct/08 20:39

Description

*start() method in FtpServer class tries to start() all the listeners one by one and it sets started=true if all of them succeeded.
If one of the listeners throws an exception when starting but some others succeded , it will not close the open listeners. Calling stop() won't have any effect in this case as 'started' is false.

*stop() method in FtpServer class returns normally when e.g., there are open connections to the FtpServer but the server is not really stopped. Calling stop() again later won't have any effect as 'started' is false.

I'm quite concerned about the fact that calling stop() won't stop the server since this means that when I undeploy my webapplication the port is still open and I need to restart the whole application server in order to have this port available (and prevent memory leaks!, I guess).