Allowing Consecutive WebSocket Reconnects #128
Merged
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.
PR Details
Description
Fixing a bug causing consecutive long-interval live intersection (STOMP websocket) reconnects to fail. The live intersection STOMP websocket handler is set to re-connect after onDisconnect and onClose. This is limited to 5 re-connects if the re-connects happen in quick succession (<10 seconds), and unlimited for longer re-connects (CDOT commonly re-connects after 30 seconds). This was causing a bug where the second 30-second re-connect would not be triggered correctly. This has been resolved.
How Has This Been Tested?
This has been tested locally
Types of changes
Checklist: