I thought the SO_REUSE is used only when the socket is in a TIME_WAIT state; i.e. only when it is closed. If there is a socket active (not closed), SO_REUSE should not have any affect and binding to the same port more than once should result in an error. I tried it on Vista 64-bit, using a 64-bit 1.5 JVM, and it did fail on the second bind attempt. Not sure if making SO_REUSE configurable would much difference, except when restarting an FTP server.
On Sat, Jun 12, 2010 at 3:57 PM, Niklas Gustavsson <[email protected]> wrote: > On Wed, Jun 9, 2010 at 3:36 PM, Niklas Gustavsson <[email protected]> > wrote: >> One reason for this could be the inconsistent handling of socket reuse >> on different OSes. FtpServer currently always enables reuse (which >> might be why your second server starts but doesn't get any traffic). >> We've discussed making this configurable, perhaps we should now >> actually do that :-) > > I've added a JIRA issue for 1.1.0 to make this configurable: > https://issues.apache.org/jira/browse/FTPSERVER-374 > > /niklas >
