Update client connection when receive a request #435
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.
Description
Sometimes when a node disconnect and reconnect, the state of connection is not set to
:connected
before a node try to send message to it and so message falls in error because the node thinks that the other node is not connected.Type of change
How Has This Been Tested?
Run 2 nodes, disconnect one and reconnect it just after, we should not see message
Cannot send message ...... :closed
after the node is reconnectedChecklist: