Thank You Gordon so much!
Still another question from me, the use-case where we wanted to use the DLQ
aka alternate-exchange is for re-submitting purposes. I have read inside the
MRG doc that rejected and/or orphaned messages must be redirected to the
alternate-exchange in case one exists.
I have tried a simple scenario where I have something like this:
1. Create a queue and one fanout exchange - bind them.
2. Create a queue like this: "myQueue; {create:receiver, delete:receiver,
assert:always, node:{x-declare:{auto-delete:true, exclusive: true,
alt-exchange: FANOUT_EXCHANGE}}}" //alternate-exchange does not work either
3. Send the message to myQueue, there I have a Listener configured, as soon
as I hit the onMessage, wait forever (while(true){} for example) without
acknowledging the message, thus the message is still inside myQueue.
Check the queue size with qpid-tool, show <ID> : myQueue has one message
which I expect to happen, because I did not do message. acknowledge() so
far.
Stop the running Thread at all - the application if you want. the queue will
be deleted because of the declaration of it, thus the message inside it will
be orphaned, thus, from my understanding it will be sent to the
alternate-exchange, which does not happen.
Is there anything that I am missing or may be this is a known-issue?
Thank you for your time,
Eugene.
--
View this message in context:
http://apache-qpid-developers.2158895.n2.nabble.com/Red-Hat-MRG-alt-exchange-tp7368166p7371373.html
Sent from the Apache Qpid developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
