race problem when starting server with port 0

[PerBothner]

I'm starting the server with a port of 0, so I can then immediately open a client of the server, without hard-wiring in a specific port. Before I start the client, I need to call getPort(). But that may not work, since the server field may not have been set yet, and that happens in a separate thread. My suggestion is to move the initial socket.bind to the start method, before the run method in the new thread. See included patch.

startserver-patch.txt

[marci4]

Hello @PerBothner
could you please open a pull request for your commit?

Thx

Greetings
marci4

[PerBothner]

I no longer use Java-WebSocket (for Domterm I use libwebsockets instead).
However, I created a quick pull request #449 .
I tested that it still compiles, but I haven't otherwise tested it.

Glad to see Java-WebSocket is seeing some love again, even though I no longer use it myself.

[marci4]

Hello @PerBothner

thx for your pull request.
Gonna test it soon :)

Closing the issue.
Greetings
marci4