On 11/21/2012 09:00 AM, eugene wrote:
Hello Gordon,
I have send the logs over email to you.
A few things : We are using mrg version 0.14; you re right about amq.fanout
would be better, but indeed we want to filter messages, it may be not
obvious from this example - a trivial one, but in the real scenario, an
amq.topic exchange is what we are after; and again createTopic is what we
have in real scenario, it was createQueue here for testing purpose only.
If there is anything I can help you with, please do let me know.
It looks like the binding for the listener is not as desired. From the log:
{ExchangeBindBody: queue=TempQueued6497a31-0ff2-4ae1-8610-3579e4dc620e;
exchange=amq.topic; binding-key=amq.topic; arguments={}; }
So that would only match messages with a routing key of amq.topic. I
would say this is a bug in the JMS client, certainly it seems an odd
choice of behaviour.
To get the example working however, perhaps try:
session.createConsumer(session.createTopic("amq.topic/TEST_QUEUE"));
(If that doesn't work send me the log again, but hopefully that will
change the binding key used above to be TEST_QUEUE, which will then
match the message that is first sent to that queue).
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
