Gary,
We've tested mandatory flag and everything seems to be working perfectly.
We hope to test DLE very soon.
Cordially,
Paul
Type: Posts; User: PMBell; Keyword(s):
Gary,
We've tested mandatory flag and everything seems to be working perfectly.
We hope to test DLE very soon.
Cordially,
Paul
That's very good news, Gary; thanks.
We'll be testing dead-letter along with mandatory flag.
-Paul
All,
Does Spring AMQP support RabbitMQ's dead-letter exchange?
Thanks.
-Paul
Hi Gary,
We are hoping to test tomorrow the functionality of the mandatory flag.
-Paul
Thanks, Gary.
Can I safely assume that, as part of the support for "mandatory" flag, you've also added support for a "return listener", or some means of handling a message rejected/returned by the...
Gary,
We are certainly willing to test and evaluate functionality ahead of time.
Please let me know what's involved and whence we can obtain a "release candidate" of 1.0.1.
Thanks.
-Paul
Terrific news, Gary - thank you.
Forgive me for asking this but, any sense for when your support for mandatory flag will be publicly available?
Cordially,
Paul
All,
Am I right to think that Spring AMQP does not expose the "mandatory" flag? For example, one can see code for RabbitMQ that sets this flag (from the Manning book):
...
Excellent; thanks.
Cool; thanks.
I'll take it to the Rabbit guys.
-Paul
What does "single" queue mean in this case; is this a matter of the queue name? For example consumer 1 binds a queue named statusQueue1 to the topic exchange with some binding key; consumer 2 binds a...
Hi Gary,
This has been a very interesting conversation, one that has revealed to me some of the subtleties inherent in a message queuing architecture.
Here's another perspective on the...
OK, I think I get it.
Questions:
Does Spring AMQP expose a means to set this "prefetch" value, or must I use the Basic.Qos call?
Is this prefetch value "distributed" across "concurrent...
Gary, thank you very much for your efforts on what are doubtless newb questions!
But despite these efforts, I confess some confusion here. When I first read this sentence:
"For instance,...
Hey Gary,
Thanks for checking the code.
In reality, I offered the high-arrival rate example as a kind of limit case. I am not convinced that, in the real world, our app will see such behavior...
Hi All,
Now that, with the help of this forum, I've gotten a simple topic exchange working, I could probably just write the code to test this issue. And I'm sure I will soon do so. But I need to...
Hi Gary,
Yeah, I've experimented with this property and some time back posted about it to the RabbitMQ list. I had observed, and the list confirmed, that this property seems to govern the number...
Hi All,
Folks on the RabbitMQ list have made clear to me that you don't treat Rabbit's queues the way you might treat a programming language Queue object. Specifically, Rabbit's queues are not...
Understood, Gary.
Thanks again.
-Paul
Dave and Gary,
By way of follow-up....
It was relatively easy to get the "raw" message approach working. Per Gary's instruction, I set the container's MessageListener to an instance of a class...
Gary (and others),
Your post arrived just before I was going to post news of some progress.
I decided to try using one of the (slightly) higher-level APIs and, rather than call .send() of a...
Dave and Gary,
Thanks again. The news about durable bindings is very good. And Gary's suggestion re defining a TopicExchange rather than a mere Exchange did the trick.
So I am very close to...
Hi again,
As promised (or threatened!) here is the consumer code. This is the constructor for my class AmqpDemoConsumer. I know that there is something wrong here.
public...
Thank you, Dave.
-Paul
Thanks Mark.
I have indeed looked at that tutorial and I think I have an
OK understanding of topic exchange, binding key and routing
key.
My difficulty or, rather, a difficulty concerns the...