-
Notifications
You must be signed in to change notification settings - Fork 357
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
Improve ServiceBus/EventHub listener shutdown #1760
Milestone
Comments
Check EventHub listener shutdown as well, since it follows the same eventing pattern |
mathewc
changed the title
Improve ServiceBus listener shutdown
Improve ServiceBus/EventHub listener shutdown
Jun 28, 2018
mathewc
added a commit
that referenced
this issue
Jul 3, 2018
mathewc
added a commit
that referenced
this issue
Jul 3, 2018
mathewc
added a commit
that referenced
this issue
Jul 3, 2018
mathewc
added a commit
that referenced
this issue
Jul 3, 2018
@mathewc is this done? The PR has been merged. |
The issue is still open because I haven't merged this to dev yet, only v2.x. I'll do that today |
mathewc
added a commit
that referenced
this issue
Jul 10, 2018
mathewc
added a commit
that referenced
this issue
Jul 10, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recent changes addressing work item #1703 now log all background errors coming from the SB MessageReceiver. This works in ensuring errors are logged during message processing.
However, during normal host shutdown, it seems disposal ordering is causing spurious errors to be logged, when there isn't a problem. E.g. the host is shutting down, the listener is stopped/disposed, and the MessageReceiver attempts one final receive operation but fails because everything is being disposed. See ICM incident #73280007.
We should clean this up so that these errors aren't logged when the host is being disposed.
See related issue: #1784
The text was updated successfully, but these errors were encountered: