Azure Service Bus Session Ordering
Let's say we have the following messages which are all part of the same Session and were placed onto the Topic in alphabetical order.
A, B, C, D
The session receiver will pick up and process message A first before moving onto B.
But what happens if message A cannot be processed. Will the receiver automatically move onto B? Or will it still respect the sequencing?
azureservicebus
asked Nov 23 '18 at 15:15
heymegaheymega
5,66852545
add a comment |
Let's say we have the following messages which are all part of the same Session and were placed onto the Topic in alphabetical order.
A, B, C, D
The session receiver will pick up and process message A first before moving onto B.
But what happens if message A cannot be processed. Will the receiver automatically move onto B? Or will it still respect the sequencing?
azureservicebus
asked Nov 23 '18 at 15:15
heymegaheymega
5,66852545
add a comment |
Let's say we have the following messages which are all part of the same Session and were placed onto the Topic in alphabetical order.
A, B, C, D
The session receiver will pick up and process message A first before moving onto B.
But what happens if message A cannot be processed. Will the receiver automatically move onto B? Or will it still respect the sequencing?
azureservicebus
asked Nov 23 '18 at 15:15
heymegaheymega
5,66852545
Let's say we have the following messages which are all part of the same Session and were placed onto the Topic in alphabetical order.
A, B, C, D
The session receiver will pick up and process message A first before moving onto B.
But what happens if message A cannot be processed. Will the receiver automatically move onto B? Or will it still respect the sequencing?
azureservicebus
azureservicebus
asked Nov 23 '18 at 15:15
heymegaheymega
5,66852545
asked Nov 23 '18 at 15:15
heymegaheymega
5,66852545
asked Nov 23 '18 at 15:15
heymegaheymega
5,66852545
asked Nov 23 '18 at 15:15
heymegaheymega
5,66852545
asked Nov 23 '18 at 15:15
heymegaheymega
5,66852545
5,66852545
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You can find the answer in Message sessions: first in, first out (FIFO):
The session lock held by the session receiver is an umbrella for the message locks used by the peek-lock settlement mode. A receiver cannot have two messages concurrently "in flight," but the messages must be processed in order. A new message can only be obtained when the prior message has been completed or dead-lettered. Abandoning a message causes the same message to be served again with the next receive operation.
In short this means that when, in your example, message A is dead-lettered because it exceeds MaxDeliveryCount, message B will be processed.
answered Nov 23 '18 at 15:24
rickvdboschrickvdbosch
4,09121626
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53449141%2fazure-service-bus-session-ordering%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can find the answer in Message sessions: first in, first out (FIFO):
The session lock held by the session receiver is an umbrella for the message locks used by the peek-lock settlement mode. A receiver cannot have two messages concurrently "in flight," but the messages must be processed in order. A new message can only be obtained when the prior message has been completed or dead-lettered. Abandoning a message causes the same message to be served again with the next receive operation.
In short this means that when, in your example, message A is dead-lettered because it exceeds MaxDeliveryCount, message B will be processed.
answered Nov 23 '18 at 15:24
rickvdboschrickvdbosch
4,09121626
add a comment |
You can find the answer in Message sessions: first in, first out (FIFO):
The session lock held by the session receiver is an umbrella for the message locks used by the peek-lock settlement mode. A receiver cannot have two messages concurrently "in flight," but the messages must be processed in order. A new message can only be obtained when the prior message has been completed or dead-lettered. Abandoning a message causes the same message to be served again with the next receive operation.
In short this means that when, in your example, message A is dead-lettered because it exceeds MaxDeliveryCount, message B will be processed.
answered Nov 23 '18 at 15:24
rickvdboschrickvdbosch
4,09121626
add a comment |
You can find the answer in Message sessions: first in, first out (FIFO):
The session lock held by the session receiver is an umbrella for the message locks used by the peek-lock settlement mode. A receiver cannot have two messages concurrently "in flight," but the messages must be processed in order. A new message can only be obtained when the prior message has been completed or dead-lettered. Abandoning a message causes the same message to be served again with the next receive operation.
In short this means that when, in your example, message A is dead-lettered because it exceeds MaxDeliveryCount, message B will be processed.
answered Nov 23 '18 at 15:24
rickvdboschrickvdbosch
4,09121626
You can find the answer in Message sessions: first in, first out (FIFO):
The session lock held by the session receiver is an umbrella for the message locks used by the peek-lock settlement mode. A receiver cannot have two messages concurrently "in flight," but the messages must be processed in order. A new message can only be obtained when the prior message has been completed or dead-lettered. Abandoning a message causes the same message to be served again with the next receive operation.
In short this means that when, in your example, message A is dead-lettered because it exceeds MaxDeliveryCount, message B will be processed.
answered Nov 23 '18 at 15:24
rickvdboschrickvdbosch
4,09121626
answered Nov 23 '18 at 15:24
rickvdboschrickvdbosch
4,09121626
answered Nov 23 '18 at 15:24
rickvdboschrickvdbosch
4,09121626
answered Nov 23 '18 at 15:24
rickvdboschrickvdbosch
4,09121626
4,09121626
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53449141%2fazure-service-bus-session-ordering%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
