Fix issue #834 by starting WebSocketWorker of the WebSocketServer in the start function #850
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I changed the constructor of the
WebSocketServer
class to only instantiate theWebSocketWorkers
but not start them. Now they are started in a foreach loop in the start function.Related Issue
This fixes the issue #834.
Motivation and Context
Now the
WebSocketWorkers
are only started when theWebSocketServer
is started instead of when it was instantiated. TheseWebSocketWorkers
run in different threads and would keep the program alive even though theWebSocketServer
was not running but simply instantiated.How Has This Been Tested?
All JUnit tests passed and the gist in the issue now properly terminates since the worker threads are never started. I did not see the need for an additional JUnit test for this small fix but would happily provide one if desired.
Types of changes
Checklist: