Repository navigation
[WIP] Support for Azure Service Bus Sessions - #8408
Closed
poornimanayar wants to merge 3 commits into
Closed
poornimanayar wants to merge 3 commits into
poornimanayar wants to merge 3 commits into
Conversation
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
github-actions
Bot
removed
the
stale
SzymonPobiega
approved these changes
Oct 19, 2026
SzymonPobiega
left a comment
SzymonPobiega
left a comment
Member
There was a problem hiding this comment.
Added some minor comments
Comment on lines
+30
to
+31
| var transport = new AzureServiceBusTransport(connectionString, topology) { Ena | ||
| bleSessions = true }; |
Member
There was a problem hiding this comment.
Suggested change
| var transport = new AzureServiceBusTransport(connectionString, topology) { Ena | |
| bleSessions = true }; | |
| var transport = new AzureServiceBusTransport(connectionString, topology) { EnableSessions = true }; |
|
|
||
| To enable ordered processing of messages, sessions must be enabled on the receiving endpoint. | ||
|
|
||
| Messages that must be processed in order must also have a `SessionId` specified. The `SessionId` can be set using the `SetSessionId` extension method on `SendOptions`. |
Member
There was a problem hiding this comment.
Suggested change
| Messages that must be processed in order must also have a `SessionId` specified. The `SessionId` can be set using the `SetSessionId` extension method on `SendOptions`. | |
| Messages that must be processed in order must also have a `SessionId` specified. The `SessionId` can be set using the `SetSessionId` extension method on `SendOptions` and `ReplyOptions`. |
|
|
||
| ## Error messages | ||
|
|
||
| When immediate retries are exhausted, messages are moved into the error queue. This can break the processing order. Retrying a message from the error queue or the DLQ does not guarantee that the message will be enqueued in its original position before it was moved to the error queue. |
Member
There was a problem hiding this comment.
Suggested change
| When immediate retries are exhausted, messages are moved into the error queue. This can break the processing order. Retrying a message from the error queue or the DLQ does not guarantee that the message will be enqueued in its original position before it was moved to the error queue. | |
| When immediate retries are exhausted, messages are moved into the error queue. This can break the processing order. Retrying a message from the error queue or the dead-letter queue (DLQ) does not guarantee that the message will be enqueued in its original position before it was moved to the error queue. |
Contributor
Author
|
Closed in favour of #8569 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
No description provided.