actor: ignore anything in unregistering state of TcpConnection
#31231
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Otherwise, we might end up with spurious "unhandled message" events which the user can nothing do against. This turned up in akka-http tests against Akka 2.6 where the interaction of TLS with TCP lead to this kind of race condition.
johanandren
approved these changes
Mar 10, 2022
jrudolph
added a commit
to jrudolph/akka-http
that referenced
this pull request
Mar 10, 2022
…ests Hoppefully, these spurious messages will further be reduced by akka/akka-core#31231.
jrudolph
added a commit
to akka/akka-http
that referenced
this pull request
Mar 10, 2022
…ests (#4074) Hoppefully, these spurious messages will further be reduced by akka/akka-core#31231.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Otherwise, we might end up with spurious "unhandled message" events which
the user can nothing do against.
This turned up in akka-http tests against Akka 2.6 where the interaction
of TLS with TCP lead to this kind of race condition.