New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make sure that causes for Disassociated(Unknown)
are consistently logged
#23023
Comments
jrudolph
added
1 - triaged
Tickets that are safe to pick up for contributing in terms of likeliness of being accepted
t:remoting
labels
May 24, 2017
jrudolph
added
3 - in progress
Someone is working on this ticket
and removed
1 - triaged
Tickets that are safe to pick up for contributing in terms of likeliness of being accepted
labels
May 29, 2017
jrudolph
added a commit
to jrudolph/akka
that referenced
this issue
Jun 7, 2017
jrudolph
added a commit
to jrudolph/akka
that referenced
this issue
Jun 14, 2017
jrudolph
added a commit
to jrudolph/akka
that referenced
this issue
Jun 14, 2017
jrudolph
added a commit
to jrudolph/akka
that referenced
this issue
Jun 14, 2017
patriknw
added a commit
that referenced
this issue
Jun 16, 2017
…ociation-reasons =rem #23023 log reasons for disassociations with debug level
patriknw
pushed a commit
that referenced
this issue
Jun 16, 2017
(cherry picked from commit cf99cf1)
patriknw
added a commit
that referenced
this issue
Jun 26, 2017
…ion-reasons-2.4-patriknw =rem #23023 log reasons for disassociations with debug level (for validation)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In old akka remoting, in most cases when a disassociation happens, the same error message will be logged because internally various causes are tracked as
Unknown
. We probably don't want to change the actual handling but we should make sure that actual causes are logged to DEBUG when aDisassociated(Unknown)
object is created to simplify debugging those issues.The text was updated successfully, but these errors were encountered: