You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case the host port (e.g. 80) is occupied on the host (let's say running another web server), you expect a bind error and then the server to close down.
The server's main thread/selector thread does shut down in that scenario, but its worker threads do not.
The reason is that in case of bind() failure, WebSocketServer.run() returns before the try-catch-finally-block which in finally contains shutdown of worker threads.
The text was updated successfully, but these errors were encountered:
In case the host port (e.g. 80) is occupied on the host (let's say running another web server), you expect a bind error and then the server to close down.
The server's main thread/selector thread does shut down in that scenario, but its worker threads do not.
The reason is that in case of bind() failure, WebSocketServer.run() returns before the try-catch-finally-block which in finally contains shutdown of worker threads.
The text was updated successfully, but these errors were encountered: