Skip to content

Conversation

Aaronontheweb
Copy link
Member

Just some logging cleanup before we push 1.1

reason.Match().With<EndpointDisassociatedException>(endpoint => PublishDisassociated())
reason.Match()
.With<EndpointDisassociatedException>(endpoint => PublishDisassociated())
.With<ShutDownAssociation>(shutdown => {}) // don't log an error for planned shutdowns
Copy link
Member Author

@Aaronontheweb Aaronontheweb Jul 5, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not present in the JVM, but I think it may be a good idea. Basically we won't log disassociations that occur as part of a shutdown (planned termination) as errors. Disabling logging for this since we get a steady drumbeat of questions from developers who are worried they're doing something wrong after seeing this error. Since the answer is "no, you're not doing anything wrong" I figured we may as well not log it as an exception to avoid the uncertainty.

The shutdown association gets logged as a DEBUG message by the EndpointManager after this, so it will still appear in the log files.

@Aaronontheweb Aaronontheweb force-pushed the akka.remote-logging-fixes branch from 1da5f4e to e76ac9b Compare July 5, 2016 17:49
@alexvaluyskiy alexvaluyskiy merged commit c38ae89 into akkadotnet:dev Jul 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants