You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by ravindra <rv...@gmail.com> on 2017/02/10 05:55:19 UTC
RabbitMQ Strange Behaviour
I am sending some messages from a Camel Route to RabbitMQ.
The URI is as follows :
to("rabbitmq://<server_ip>:5672/ravindra_test_exchange?autoDelete=false&routingKey=abc")
I have the created an exchange ravindra_test_exchange and a queue
ravindra_test_queue_abc.
The exchange is bound to the queue with routing key "abc".
I expected that the messages will be routed to the queue
ravindra_test_queue_abc.
But it creates another queue with random name, binds the exchange with the
new queue and sends messages to both the queues.
<http://camel.465427.n5.nabble.com/file/n5793741/Queue.jpg>
<http://camel.465427.n5.nabble.com/file/n5793741/Exchange.jpg>
Why is it behaving in this way? Do I need to specify any other property in
the URI?
--
View this message in context: http://camel.465427.n5.nabble.com/RabbitMQ-Strange-Behaviour-tp5793741.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: RabbitMQ Strange Behaviour
Posted by souciance <so...@gmail.com>.
Well I have not experienced it that way. Like I said, that temporary queue
is for request-reply processing. If you want to fire and forget you need to
specify that the exchange pattern is InOnly.
On Fri, Feb 10, 2017 at 8:58 AM, ravindra [via Camel] <
ml-node+s465427n5793745h58@n5.nabble.com> wrote:
> I am using RabbitMQ 3.6.6, Erlang R16B03.
>
> When I specify the URI as :
> rabbitmq://<server_ip>:5672/ravindra_test_exchange?
> autoDelete=false&routingKey=abc&queue=ravindra_test_queue_abc
>
> Then it sends only to the expected queue.
> But isn't it wrong, that I need to specify the exchange, routing key and
> the queue as well.
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/RabbitMQ-Strange-
> Behaviour-tp5793741p5793745.html
> To start a new topic under Camel - Users, email
> ml-node+s465427n465428h31@n5.nabble.com
> To unsubscribe from Camel - Users, click here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=465428&code=c291Y2lhbmNlLmVxZGFtLnJhc2h0aUBnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://camel.465427.n5.nabble.com/RabbitMQ-Strange-Behaviour-tp5793741p5793746.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: RabbitMQ Strange Behaviour
Posted by ravindra <rv...@gmail.com>.
I am using RabbitMQ 3.6.6, Erlang R16B03.
When I specify the URI as :
rabbitmq://<server_ip>:5672/ravindra_test_exchange?autoDelete=false&routingKey=abc&queue=ravindra_test_queue_abc
Then it sends only to the expected queue.
But isn't it wrong, that I need to specify the exchange, routing key and the
queue as well.
--
View this message in context: http://camel.465427.n5.nabble.com/RabbitMQ-Strange-Behaviour-tp5793741p5793745.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: RabbitMQ Strange Behaviour
Posted by souciance <so...@gmail.com>.
Which Camel version are you on? I would not expect it to send to the
temporary queue which is created when you do request-reply messaging.
On Fri, Feb 10, 2017 at 6:55 AM, ravindra [via Camel] <
ml-node+s465427n5793741h34@n5.nabble.com> wrote:
> I am sending some messages from a Camel Route to RabbitMQ.
>
> The URI is as follows :
>
> to("rabbitmq://<server_ip>:5672/ravindra_test_exchange?
> autoDelete=false&routingKey=abc")
>
> I have the created an exchange ravindra_test_exchange and a queue
> ravindra_test_queue_abc.
> The exchange is bound to the queue with routing key "abc".
>
> I expected that the messages will be routed to the queue
> ravindra_test_queue_abc.
> But it creates another queue with random name, binds the exchange with the
> new queue and sends messages to both the queues.
>
>
>
>
>
>
> Why is it behaving in this way? Do I need to specify any other property in
> the URI?
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/RabbitMQ-Strange-
> Behaviour-tp5793741.html
> To start a new topic under Camel - Users, email
> ml-node+s465427n465428h31@n5.nabble.com
> To unsubscribe from Camel - Users, click here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=465428&code=c291Y2lhbmNlLmVxZGFtLnJhc2h0aUBnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://camel.465427.n5.nabble.com/RabbitMQ-Strange-Behaviour-tp5793741p5793742.html
Sent from the Camel - Users mailing list archive at Nabble.com.