No warning starting Jetty on port already in use (on Windows)
The work around is to use the setReuseAddress(false) on the SelectChannelConnector. By default, this value is set to
true, and enables the socket option
SO_REUSEADDRESS. This means that a socket may be opened, even if there is previous close (ie the port is in
TIME_WAIT state) still pending on that socket. Setting it to
false does not permit the socket to be re-opened in that state, but it also allows an Exception to be thrown if the socket is in use, eg by another Jetty instance.