Stefan Burkard created CAMEL-15123:
--------------------------------------
Summary: camel-rabbitmq creates its own queue when properties do
not match
Key: CAMEL-15123
URL: https://issues.apache.org/jira/browse/CAMEL-15123
Project: Camel
Issue Type: Improvement
Components: camel-rabbitmq
Affects Versions: 3.3.0
Reporter: Stefan Burkard
According to [this question and answer on
StackOverflow|https://stackoverflow.com/a/26509746/8035582], camel-rabbitmq
creates its own queue instead of using an existing one when the queue
properties and the connection string properties do not match.
This is especially confusing when the {{queue}} property is provided, but the
consumer does not consume or produce to/from the predefined queue.
And it can be tricky too: *differences can be hidden in default values of the
Camel consumer*. In the mentioned SO answer, the property {{autoDelete}} was
the difference (by default {{true}} in Camel, but {{false}} on the predefined
queue).
>From a user perspective, camel-rabbitmq should always connect to the
>predefined queue if the queue name and the rabbitmq exchange match an existing
>exchange/queue. Even if some other properties do not match. It could perhaps
>warn in the logs about any differences in properties.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
