JBoss AMQ / ActiveMQ Artemis: Pre-configure Durable Subscribers
I have a Red Hat AMQ (which is based on ActiveMQ Artemis) broker and I would like to make use of durable subscription (or equivalent) feature, so that I will have multiple OpenWire JMS subscribers subscribing to the events of our application which will be delivered to them reliably.
I would like to pre-configure subscribers, so to save me trouble in initial application startup. I want to avoid the case for initial application start up where the main application starts running and publishing events before our durable subscribers perform their initial subscription.
I also wants to avoid explicitly ordering start up sequence of my processes.
Is there any way I can pre-configure durable subscribers? In ordinary ActiveMQ (not Artemis), there is feature like Virtual Topics which (kind of) solve the problem.
What is the preferred solution for ActiveMQ Artemis?
activemq-artemis amq durable-subscription
edited Nov 27 '18 at 2:50
Justin Bertram
4,0321519
asked Nov 23 '18 at 7:33
Adrian ShumAdrian Shum
29k763107
|
show 2 more comments
I have a Red Hat AMQ (which is based on ActiveMQ Artemis) broker and I would like to make use of durable subscription (or equivalent) feature, so that I will have multiple OpenWire JMS subscribers subscribing to the events of our application which will be delivered to them reliably.
I would like to pre-configure subscribers, so to save me trouble in initial application startup. I want to avoid the case for initial application start up where the main application starts running and publishing events before our durable subscribers perform their initial subscription.
I also wants to avoid explicitly ordering start up sequence of my processes.
Is there any way I can pre-configure durable subscribers? In ordinary ActiveMQ (not Artemis), there is feature like Virtual Topics which (kind of) solve the problem.
What is the preferred solution for ActiveMQ Artemis?
activemq-artemis amq durable-subscription
edited Nov 27 '18 at 2:50
Justin Bertram
4,0321519
asked Nov 23 '18 at 7:33
Adrian ShumAdrian Shum
29k763107
What kind of client are you using?
– Justin Bertram
Nov 23 '18 at 18:21
Just wonder how this is related to the question?
– Adrian Shum
Nov 23 '18 at 23:37
Because the name of the queue created for a "durable subscription" may be different depending on which client is being used. Also, did you read the Artemis documentation on this?
– Justin Bertram
Nov 24 '18 at 2:13
FYI - the STOMP chapter in the Artemis documentation also discusses this.
– Justin Bertram
Nov 26 '18 at 3:56
I am going to use it with JMS (ah... I should have mentioned it in the question). Lemme keep STOMP in my broker config and try if this works, thanks.
– Adrian Shum
Nov 26 '18 at 8:39
|
show 2 more comments
I have a Red Hat AMQ (which is based on ActiveMQ Artemis) broker and I would like to make use of durable subscription (or equivalent) feature, so that I will have multiple OpenWire JMS subscribers subscribing to the events of our application which will be delivered to them reliably.
I would like to pre-configure subscribers, so to save me trouble in initial application startup. I want to avoid the case for initial application start up where the main application starts running and publishing events before our durable subscribers perform their initial subscription.
I also wants to avoid explicitly ordering start up sequence of my processes.
Is there any way I can pre-configure durable subscribers? In ordinary ActiveMQ (not Artemis), there is feature like Virtual Topics which (kind of) solve the problem.
What is the preferred solution for ActiveMQ Artemis?
activemq-artemis amq durable-subscription
edited Nov 27 '18 at 2:50
Justin Bertram
4,0321519
asked Nov 23 '18 at 7:33
Adrian ShumAdrian Shum
29k763107
I have a Red Hat AMQ (which is based on ActiveMQ Artemis) broker and I would like to make use of durable subscription (or equivalent) feature, so that I will have multiple OpenWire JMS subscribers subscribing to the events of our application which will be delivered to them reliably.
I would like to pre-configure subscribers, so to save me trouble in initial application startup. I want to avoid the case for initial application start up where the main application starts running and publishing events before our durable subscribers perform their initial subscription.
I also wants to avoid explicitly ordering start up sequence of my processes.
Is there any way I can pre-configure durable subscribers? In ordinary ActiveMQ (not Artemis), there is feature like Virtual Topics which (kind of) solve the problem.
What is the preferred solution for ActiveMQ Artemis?
activemq-artemis amq durable-subscription
activemq-artemis amq durable-subscription
edited Nov 27 '18 at 2:50
Justin Bertram
4,0321519
asked Nov 23 '18 at 7:33
Adrian ShumAdrian Shum
29k763107
edited Nov 27 '18 at 2:50
Justin Bertram
4,0321519
asked Nov 23 '18 at 7:33
Adrian ShumAdrian Shum
29k763107
edited Nov 27 '18 at 2:50
Justin Bertram
4,0321519
edited Nov 27 '18 at 2:50
Justin Bertram
4,0321519
edited Nov 27 '18 at 2:50
Justin Bertram
4,0321519
4,0321519
asked Nov 23 '18 at 7:33
Adrian ShumAdrian Shum
29k763107
asked Nov 23 '18 at 7:33
Adrian ShumAdrian Shum
29k763107
asked Nov 23 '18 at 7:33
Adrian ShumAdrian Shum
29k763107
29k763107
What kind of client are you using?
– Justin Bertram
Nov 23 '18 at 18:21
Just wonder how this is related to the question?
– Adrian Shum
Nov 23 '18 at 23:37
Because the name of the queue created for a "durable subscription" may be different depending on which client is being used. Also, did you read the Artemis documentation on this?
– Justin Bertram
Nov 24 '18 at 2:13
FYI - the STOMP chapter in the Artemis documentation also discusses this.
– Justin Bertram
Nov 26 '18 at 3:56
I am going to use it with JMS (ah... I should have mentioned it in the question). Lemme keep STOMP in my broker config and try if this works, thanks.
– Adrian Shum
Nov 26 '18 at 8:39
|
show 2 more comments
What kind of client are you using?
– Justin Bertram
Nov 23 '18 at 18:21
Just wonder how this is related to the question?
– Adrian Shum
Nov 23 '18 at 23:37
Because the name of the queue created for a "durable subscription" may be different depending on which client is being used. Also, did you read the Artemis documentation on this?
– Justin Bertram
Nov 24 '18 at 2:13
FYI - the STOMP chapter in the Artemis documentation also discusses this.
– Justin Bertram
Nov 26 '18 at 3:56
I am going to use it with JMS (ah... I should have mentioned it in the question). Lemme keep STOMP in my broker config and try if this works, thanks.
– Adrian Shum
Nov 26 '18 at 8:39
What kind of client are you using?
– Justin Bertram
Nov 23 '18 at 18:21
What kind of client are you using?
– Justin Bertram
Nov 23 '18 at 18:21
Just wonder how this is related to the question?
– Adrian Shum
Nov 23 '18 at 23:37
Just wonder how this is related to the question?
– Adrian Shum
Nov 23 '18 at 23:37
Because the name of the queue created for a "durable subscription" may be different depending on which client is being used. Also, did you read the Artemis documentation on this?
– Justin Bertram
Nov 24 '18 at 2:13
Because the name of the queue created for a "durable subscription" may be different depending on which client is being used. Also, did you read the Artemis documentation on this?
– Justin Bertram
Nov 24 '18 at 2:13
FYI - the STOMP chapter in the Artemis documentation also discusses this.
– Justin Bertram
Nov 26 '18 at 3:56
FYI - the STOMP chapter in the Artemis documentation also discusses this.
– Justin Bertram
Nov 26 '18 at 3:56
I am going to use it with JMS (ah... I should have mentioned it in the question). Lemme keep STOMP in my broker config and try if this works, thanks.
– Adrian Shum
Nov 26 '18 at 8:39
I am going to use it with JMS (ah... I should have mentioned it in the question). Lemme keep STOMP in my broker config and try if this works, thanks.
– Adrian Shum
Nov 26 '18 at 8:39
|
show 2 more comments
1 Answer
1
active
oldest
votes
It is possible to pre-configure durable subscriptions since the OpenWire implementation creates the queue used for the durable subscription in a deterministic way (i.e. using the format of client-id.subscription-name). For example, if you wanted to configure a durable subscription on the address myAddress with a client-id of myclientid and a subscription name of mysubscription then configure the durable subscription:
<addresses>
<address name="myAddress">
<multicast>
<queue name="myclientid.mysubscription"/>
</multicast>
</address>
</addresses>
answered Nov 27 '18 at 3:32
Justin BertramJustin Bertram
4,0321519
Thanks a lot. It works as expected. Sorry for the belated acceptance as I didn't have chance to test that out till now :)
– Adrian Shum
Dec 10 '18 at 9:39
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%2f53442393%2fjboss-amq-activemq-artemis-pre-configure-durable-subscribers%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
It is possible to pre-configure durable subscriptions since the OpenWire implementation creates the queue used for the durable subscription in a deterministic way (i.e. using the format of client-id.subscription-name). For example, if you wanted to configure a durable subscription on the address myAddress with a client-id of myclientid and a subscription name of mysubscription then configure the durable subscription:
<addresses>
<address name="myAddress">
<multicast>
<queue name="myclientid.mysubscription"/>
</multicast>
</address>
</addresses>
answered Nov 27 '18 at 3:32
Justin BertramJustin Bertram
4,0321519
Thanks a lot. It works as expected. Sorry for the belated acceptance as I didn't have chance to test that out till now :)
– Adrian Shum
Dec 10 '18 at 9:39
add a comment |
It is possible to pre-configure durable subscriptions since the OpenWire implementation creates the queue used for the durable subscription in a deterministic way (i.e. using the format of client-id.subscription-name). For example, if you wanted to configure a durable subscription on the address myAddress with a client-id of myclientid and a subscription name of mysubscription then configure the durable subscription:
<addresses>
<address name="myAddress">
<multicast>
<queue name="myclientid.mysubscription"/>
</multicast>
</address>
</addresses>
answered Nov 27 '18 at 3:32
Justin BertramJustin Bertram
4,0321519
Thanks a lot. It works as expected. Sorry for the belated acceptance as I didn't have chance to test that out till now :)
– Adrian Shum
Dec 10 '18 at 9:39
add a comment |
It is possible to pre-configure durable subscriptions since the OpenWire implementation creates the queue used for the durable subscription in a deterministic way (i.e. using the format of client-id.subscription-name). For example, if you wanted to configure a durable subscription on the address myAddress with a client-id of myclientid and a subscription name of mysubscription then configure the durable subscription:
<addresses>
<address name="myAddress">
<multicast>
<queue name="myclientid.mysubscription"/>
</multicast>
</address>
</addresses>
answered Nov 27 '18 at 3:32
Justin BertramJustin Bertram
4,0321519
It is possible to pre-configure durable subscriptions since the OpenWire implementation creates the queue used for the durable subscription in a deterministic way (i.e. using the format of client-id.subscription-name). For example, if you wanted to configure a durable subscription on the address myAddress with a client-id of myclientid and a subscription name of mysubscription then configure the durable subscription:
<addresses>
<address name="myAddress">
<multicast>
<queue name="myclientid.mysubscription"/>
</multicast>
</address>
</addresses>
answered Nov 27 '18 at 3:32
Justin BertramJustin Bertram
4,0321519
answered Nov 27 '18 at 3:32
Justin BertramJustin Bertram
4,0321519
answered Nov 27 '18 at 3:32
Justin BertramJustin Bertram
4,0321519
answered Nov 27 '18 at 3:32
Justin BertramJustin Bertram
4,0321519
4,0321519
Thanks a lot. It works as expected. Sorry for the belated acceptance as I didn't have chance to test that out till now :)
– Adrian Shum
Dec 10 '18 at 9:39
add a comment |
Thanks a lot. It works as expected. Sorry for the belated acceptance as I didn't have chance to test that out till now :)
– Adrian Shum
Dec 10 '18 at 9:39
Thanks a lot. It works as expected. Sorry for the belated acceptance as I didn't have chance to test that out till now :)
– Adrian Shum
Dec 10 '18 at 9:39
Thanks a lot. It works as expected. Sorry for the belated acceptance as I didn't have chance to test that out till now :)
– Adrian Shum
Dec 10 '18 at 9:39
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%2f53442393%2fjboss-amq-activemq-artemis-pre-configure-durable-subscribers%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
What kind of client are you using?
– Justin Bertram
Nov 23 '18 at 18:21
Just wonder how this is related to the question?
– Adrian Shum
Nov 23 '18 at 23:37
Because the name of the queue created for a "durable subscription" may be different depending on which client is being used. Also, did you read the Artemis documentation on this?
– Justin Bertram
Nov 24 '18 at 2:13
FYI - the STOMP chapter in the Artemis documentation also discusses this.
– Justin Bertram
Nov 26 '18 at 3:56
I am going to use it with JMS (ah... I should have mentioned it in the question). Lemme keep STOMP in my broker config and try if this works, thanks.
– Adrian Shum
Nov 26 '18 at 8:39