[azservicebus] Create a programmatically useful code for when a session is not available #19113
Conversation
This file contains 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
added 2 commits
September 13, 2022 18:18
…osoft:timeout error from Service Bus. The primary use is if we are doing an AcceptNextSessionFor<Entity>() and there aren't any available sessions. This should allow customers to figure out if there's a genuine failure or if their session-enabled queue/subscription is "empty". Fixes Azure#19039
…ame code now for AcceptNext().
|
/azp run go - azservicebus |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ryepup
reviewed
Sep 14, 2022
Co-authored-by: Ryan Davis <ryepup@gmail.com>
jhendrixMSFT
approved these changes
Sep 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adding a new error Code (
CodeTimeout) for when we get back acom.microsoft:timeouterror from Service Bus. The primary use is if we are doing anAcceptNextSessionFor<Entity>()and there aren't any available sessions.This should allow customers to figure out if there's a genuine failure or if their session-enabled queue/subscription is simply "empty".
This also improves the tests and adds in some more customer exposed examples for reading through a a queue of sessions.
Fixes #19039