Handle reserved server address

[ripla]

There is rare exception that has existed for a long while:

Error:
Jetty lifecycle failed
java.net.BindException: Address already in use
        at java.base/sun.nio.ch.Net.bind0(Native Method)
        at java.base/sun.nio.ch.Net.bind(Net.java:433)
        at java.base/sun.nio.ch.Net.bind(Net.java:425)
        at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:225)
        at java.base/sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:317)
        at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
        at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:235)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.server.Server.doStart(Server.java:401)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at com.vaadin.designer2.server.AbstractEditorApplicationServer.start(AbstractEditorApplicationServer.java:433)
        at com.vaadin.designer2.server.AbstractEditorApplicationServer.start(AbstractEditorApplicationServer.java:410)
        at com.vaadin.designer2.server.AbstractEditorApplicationServer.registerContextPath(AbstractEditorApplicationServer.java:176)

Assuming the error situation is reasonable, the exception should be handled in a graceful way. In an optimal scenario, Designer would just try another port until a free one is found.

[ripla]

Note that this affects both editors since they use the same server.

[qtdzz]

A user reported the same stacktrace after opening a created Design in a newly created vaadin-archetype-application-multimodule project.

Java: 1.8.0_152 
Eclipse: org.eclipse.epp.package.jee.product 4.7.3.20180405-1200 
Designer: 3.0.1 
Vaadin: 8.4.1

[mjvesa]

Another report of the same issue when a user has opened an existing project using a freshly updated designer.

OS: Windows 10 10.0 amd64
Browser: Mozilla/5.0 (Windows NT 6.2; Win64; x64; Trident/7.0; ASU2JS; rv:11.0) like Gecko
Java: 1.8.0_171
Eclipse: org.eclipse.epp.package.jee.product 4.7.3.20180405-1200
Designer: 3.0.2 

[tanbt]

There're two problems in Eclipse regarding this issue.

1. There's a thread still running after closing/removing the project. This thread restarts the server again and again.

Reproduce:

• Open a Vaadin 10 project
• Open a design
• Close or remove the project
  Actual:
• Eclipse log shows still that the server is restarted again and again with a new port
  Expect:
• Nothing happens. The server should completely be stopped.

2 . The BindException: Address already in use

Reproduce:

• Open a Vaadin 10 project
• Open a design
• Close or remove the project
• Open/Import the project again
• Open a design
  Actual:
• Eclipse log shows the BindException and the editor keeps flashing.
  Expect:
• No exception.