Dynamically create queues and topics from the client with Qpid using AMQP 1.0Durable Subscriber is not receiving messages from TopicAMQP (Qpid) one to many queueClient failover for qpid/amqp jms client?AMQP QPID client connector?Creating subscriptions on Azure ServiceBus with QPID JMS (AMQP 1.0)AMQP 1.0 Qpid JMS and an Issue with Failover/Reconnectamqp qpid 1.0 protocol uri formatJMS QPID Queue vs TopicInteroperability between AMQP 1.0 and 0-* clientsQPID AMQP client - Bind virtual IP to local
Is it possible to encode a message in such a way that can only be read by someone or something capable of seeing into the very near future?
1, 2, 4, 8, 16, ... 33?
How to find the sum of elements at compile time?
How to deal with my team leader who keeps calling me about project updates even though I am on leave for personal reasons?
Social leper versus social leopard
Cut a cake into 3 equal portions with only a knife
What happens if nobody can form a government in Israel?
I reverse the source code, you negate the output!
Do we know the situation in Britain before Sealion (summer 1940)?
Would Taiwan and China's dispute be solved if Taiwan gave up being the Republic of China?
How to manage expenditure when billing cycles and paycheck cycles are not aligned?
Resolving moral conflict
Did Apollo carry and use WD40?
I reverse the source code, you negate the input!
Late 1970's and 6502 chip facilities for operating systems
How to make interviewee comfortable interviewing in lounge chairs
Should I complain to HR about being mocked for request I made
Writing a letter of recommendation for a mediocre student
Can the U.S. president make military decisions without consulting anyone?
How does IBM's 53-bit quantum computer compare to classical ones for cryptanalytic tasks?
Guitar tuning (EADGBE), "perfect" fourths?
Norwegian refuses EU delay (4.7 hours) compensation because it turned out there was nothing wrong with the aircraft
In a folk jam session, when asked which key my non-transposing chromatic instrument (like a violin) is in, what do I answer?
Are there non JavaScript ways to hide HTML source code?
Dynamically create queues and topics from the client with Qpid using AMQP 1.0
Durable Subscriber is not receiving messages from TopicAMQP (Qpid) one to many queueClient failover for qpid/amqp jms client?AMQP QPID client connector?Creating subscriptions on Azure ServiceBus with QPID JMS (AMQP 1.0)AMQP 1.0 Qpid JMS and an Issue with Failover/Reconnectamqp qpid 1.0 protocol uri formatJMS QPID Queue vs TopicInteroperability between AMQP 1.0 and 0-* clientsQPID AMQP client - Bind virtual IP to local
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I'm trying to upgrade our old Qpid setup (AMQP 0-X based) to the latest proton version of Qpid based on AMQP 1.0 and running into an issue with dynamically creating durable or non-durable queues/topics from the client. We used to be able to do this utilizing Spring's jms-generic:queue:someQueueName (or topic in some of our cases) which would ultimately create the queue or topic for us after going through the dynamic destination resolver. However, this no longer seems to be the case as createQueue/Topic doesn't create the actual queue or topic anymore (at least what I've read on the JMS docs regarding createQueue/Topic).
So my concerns ultimately boil down to:
1) Is it still possible to dynamically create queues and topics using the newest Qpid JMS and Broker-J,
2) and if so, how can I using Qpid JMS and Broker-J to make it happen?
Thanks for your responses in advance.
Side note: I fully realize this is a pretty barebones, high-level overview, so I can provide more details as needed. I'm just hoping someone might be able to definitively answer (1) before I try moving on with (2).
spring jms amqp qpid
asked Mar 28 at 15:38
Captain n00bCaptain n00b
231 silver badge8 bronze badges
add a comment
|
I'm trying to upgrade our old Qpid setup (AMQP 0-X based) to the latest proton version of Qpid based on AMQP 1.0 and running into an issue with dynamically creating durable or non-durable queues/topics from the client. We used to be able to do this utilizing Spring's jms-generic:queue:someQueueName (or topic in some of our cases) which would ultimately create the queue or topic for us after going through the dynamic destination resolver. However, this no longer seems to be the case as createQueue/Topic doesn't create the actual queue or topic anymore (at least what I've read on the JMS docs regarding createQueue/Topic).
So my concerns ultimately boil down to:
1) Is it still possible to dynamically create queues and topics using the newest Qpid JMS and Broker-J,
2) and if so, how can I using Qpid JMS and Broker-J to make it happen?
Thanks for your responses in advance.
Side note: I fully realize this is a pretty barebones, high-level overview, so I can provide more details as needed. I'm just hoping someone might be able to definitively answer (1) before I try moving on with (2).
spring jms amqp qpid
asked Mar 28 at 15:38
Captain n00bCaptain n00b
231 silver badge8 bronze badges
add a comment
|
I'm trying to upgrade our old Qpid setup (AMQP 0-X based) to the latest proton version of Qpid based on AMQP 1.0 and running into an issue with dynamically creating durable or non-durable queues/topics from the client. We used to be able to do this utilizing Spring's jms-generic:queue:someQueueName (or topic in some of our cases) which would ultimately create the queue or topic for us after going through the dynamic destination resolver. However, this no longer seems to be the case as createQueue/Topic doesn't create the actual queue or topic anymore (at least what I've read on the JMS docs regarding createQueue/Topic).
So my concerns ultimately boil down to:
1) Is it still possible to dynamically create queues and topics using the newest Qpid JMS and Broker-J,
2) and if so, how can I using Qpid JMS and Broker-J to make it happen?
Thanks for your responses in advance.
Side note: I fully realize this is a pretty barebones, high-level overview, so I can provide more details as needed. I'm just hoping someone might be able to definitively answer (1) before I try moving on with (2).
spring jms amqp qpid
asked Mar 28 at 15:38
Captain n00bCaptain n00b
231 silver badge8 bronze badges
I'm trying to upgrade our old Qpid setup (AMQP 0-X based) to the latest proton version of Qpid based on AMQP 1.0 and running into an issue with dynamically creating durable or non-durable queues/topics from the client. We used to be able to do this utilizing Spring's jms-generic:queue:someQueueName (or topic in some of our cases) which would ultimately create the queue or topic for us after going through the dynamic destination resolver. However, this no longer seems to be the case as createQueue/Topic doesn't create the actual queue or topic anymore (at least what I've read on the JMS docs regarding createQueue/Topic).
So my concerns ultimately boil down to:
1) Is it still possible to dynamically create queues and topics using the newest Qpid JMS and Broker-J,
2) and if so, how can I using Qpid JMS and Broker-J to make it happen?
Thanks for your responses in advance.
Side note: I fully realize this is a pretty barebones, high-level overview, so I can provide more details as needed. I'm just hoping someone might be able to definitively answer (1) before I try moving on with (2).
spring jms amqp qpid
spring jms amqp qpid
asked Mar 28 at 15:38
Captain n00bCaptain n00b
231 silver badge8 bronze badges
asked Mar 28 at 15:38
Captain n00bCaptain n00b
231 silver badge8 bronze badges
asked Mar 28 at 15:38
Captain n00bCaptain n00b
231 silver badge8 bronze badges
asked Mar 28 at 15:38
Captain n00bCaptain n00b
231 silver badge8 bronze badges
asked Mar 28 at 15:38
Captain n00bCaptain n00b
231 silver badge8 bronze badges
231 silver badge8 bronze badges
add a comment
|
add a comment
|
1 Answer
1
active
oldest
votes
The new JMS client does not have a provision for automatically creating queues based on the address string; in part this is because AMQP 1.0 does not yet define a common mechanism for creating queues as such.
Qpid Broker-J does support the creation of queues/exchanges/etc. through a management protocol - but other brokers/services have not standardised on this yet.
The Broker system tests use AMQP management for dynamically creating entities... https://github.com/apache/qpid-broker-j/blob/master/systests/qpid-systests-jms-core/src/main/java/org/apache/qpid/systests/AmqpManagementFacade.java
answered Apr 2 at 9:42
Rob GodfreyRob Godfrey
1411 bronze badge
Thanks for the comment, @Rob. My apologies for not responding sooner. I actually found this information the day I originally asked the question, but forgot to update with my findings. I was able to get Broker-J to create my queues and topics dynamically after making minor changes to my queue and topic uris based on some clues in the Broker-J source code. Now I just need to figure out how tell the broker to make them durable!
– Captain n00b
Apr 5 at 17:55
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/4.0/"u003ecc by-sa 4.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%2f55401602%2fdynamically-create-queues-and-topics-from-the-client-with-qpid-using-amqp-1-0%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
The new JMS client does not have a provision for automatically creating queues based on the address string; in part this is because AMQP 1.0 does not yet define a common mechanism for creating queues as such.
Qpid Broker-J does support the creation of queues/exchanges/etc. through a management protocol - but other brokers/services have not standardised on this yet.
The Broker system tests use AMQP management for dynamically creating entities... https://github.com/apache/qpid-broker-j/blob/master/systests/qpid-systests-jms-core/src/main/java/org/apache/qpid/systests/AmqpManagementFacade.java
answered Apr 2 at 9:42
Rob GodfreyRob Godfrey
1411 bronze badge
Thanks for the comment, @Rob. My apologies for not responding sooner. I actually found this information the day I originally asked the question, but forgot to update with my findings. I was able to get Broker-J to create my queues and topics dynamically after making minor changes to my queue and topic uris based on some clues in the Broker-J source code. Now I just need to figure out how tell the broker to make them durable!
– Captain n00b
Apr 5 at 17:55
add a comment
|
The new JMS client does not have a provision for automatically creating queues based on the address string; in part this is because AMQP 1.0 does not yet define a common mechanism for creating queues as such.
Qpid Broker-J does support the creation of queues/exchanges/etc. through a management protocol - but other brokers/services have not standardised on this yet.
The Broker system tests use AMQP management for dynamically creating entities... https://github.com/apache/qpid-broker-j/blob/master/systests/qpid-systests-jms-core/src/main/java/org/apache/qpid/systests/AmqpManagementFacade.java
answered Apr 2 at 9:42
Rob GodfreyRob Godfrey
1411 bronze badge
Thanks for the comment, @Rob. My apologies for not responding sooner. I actually found this information the day I originally asked the question, but forgot to update with my findings. I was able to get Broker-J to create my queues and topics dynamically after making minor changes to my queue and topic uris based on some clues in the Broker-J source code. Now I just need to figure out how tell the broker to make them durable!
– Captain n00b
Apr 5 at 17:55
add a comment
|
The new JMS client does not have a provision for automatically creating queues based on the address string; in part this is because AMQP 1.0 does not yet define a common mechanism for creating queues as such.
Qpid Broker-J does support the creation of queues/exchanges/etc. through a management protocol - but other brokers/services have not standardised on this yet.
The Broker system tests use AMQP management for dynamically creating entities... https://github.com/apache/qpid-broker-j/blob/master/systests/qpid-systests-jms-core/src/main/java/org/apache/qpid/systests/AmqpManagementFacade.java
answered Apr 2 at 9:42
Rob GodfreyRob Godfrey
1411 bronze badge
The new JMS client does not have a provision for automatically creating queues based on the address string; in part this is because AMQP 1.0 does not yet define a common mechanism for creating queues as such.
Qpid Broker-J does support the creation of queues/exchanges/etc. through a management protocol - but other brokers/services have not standardised on this yet.
The Broker system tests use AMQP management for dynamically creating entities... https://github.com/apache/qpid-broker-j/blob/master/systests/qpid-systests-jms-core/src/main/java/org/apache/qpid/systests/AmqpManagementFacade.java
answered Apr 2 at 9:42
Rob GodfreyRob Godfrey
1411 bronze badge
answered Apr 2 at 9:42
Rob GodfreyRob Godfrey
1411 bronze badge
answered Apr 2 at 9:42
Rob GodfreyRob Godfrey
1411 bronze badge
answered Apr 2 at 9:42
Rob GodfreyRob Godfrey
1411 bronze badge
1411 bronze badge
Thanks for the comment, @Rob. My apologies for not responding sooner. I actually found this information the day I originally asked the question, but forgot to update with my findings. I was able to get Broker-J to create my queues and topics dynamically after making minor changes to my queue and topic uris based on some clues in the Broker-J source code. Now I just need to figure out how tell the broker to make them durable!
– Captain n00b
Apr 5 at 17:55
add a comment
|
Thanks for the comment, @Rob. My apologies for not responding sooner. I actually found this information the day I originally asked the question, but forgot to update with my findings. I was able to get Broker-J to create my queues and topics dynamically after making minor changes to my queue and topic uris based on some clues in the Broker-J source code. Now I just need to figure out how tell the broker to make them durable!
– Captain n00b
Apr 5 at 17:55
Thanks for the comment, @Rob. My apologies for not responding sooner. I actually found this information the day I originally asked the question, but forgot to update with my findings. I was able to get Broker-J to create my queues and topics dynamically after making minor changes to my queue and topic uris based on some clues in the Broker-J source code. Now I just need to figure out how tell the broker to make them durable!
– Captain n00b
Apr 5 at 17:55
Thanks for the comment, @Rob. My apologies for not responding sooner. I actually found this information the day I originally asked the question, but forgot to update with my findings. I was able to get Broker-J to create my queues and topics dynamically after making minor changes to my queue and topic uris based on some clues in the Broker-J source code. Now I just need to figure out how tell the broker to make them durable!
– Captain n00b
Apr 5 at 17:55
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%2f55401602%2fdynamically-create-queues-and-topics-from-the-client-with-qpid-using-amqp-1-0%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
