[ https://issues.jboss.org/browse/JBIDE-20684?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-20684: --------------------------------------- The problem happens even without the new quick launcher: as soon as a connection has been established with a browser, a socket exists even though the underlying Jetty server has been stopped, the socket is still open (probably in a {{CLOSE_WAIT}} state) and this prevent immediate server restart. In the short term, I can see 2 scenario here: 1 - wait until the socket is really closed before restarting the server. This can take up to 30s. This does not block the UI but the user will see the LiveReload server in "Stopping..." state 2 - use the serverConnection.setReuseAddress(true) to immediately reuse the bind address, but this was explicitely disabled a while ago to prevent multiple instances of LiveReload or other programs (eg: guard-livereload) to use the same port. Plus the requests sent by the browser may not be processed by the new instance of the LiveReload server. In the longer term (ie, for 4.3.x or 4.4.x), we could add an option in the server config to let the user enable/disable the "reuse address" flag. [~akazakov], [~maxandersen], WDYT ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)