Detect disconnected subscriber #426
Open
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.
I encountered the issue with a subscriber reconnecting to a topic. In this request, I provided my solution to this problem.
The file contains a test that creates two threads: one for the
publisherand one for thesubscriber.They pass a structure TestType to the topic with two fields: one
id: i32and the otherMassage: String.After a
publisherandsubscriberconnect to the sametopic, thepublishersends its messages totopic, and the subscriber reads them using a DataReader. After 2 seconds, the subscriber deletes the thread associated with the DataReader, which it started at the very beginning, thereby simulating a disconnection from reading, and after 2 seconds, it starts it again, simulating a reconnection.While running tests, I didn't encounter any issues related to Timeout error.
I hope you find this material useful.
To check all the outputs for this test, you need to run:
cargo test --test detect_disconnected_subscriber -- --show-outputand you get this result:
