Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Information Provided
-
3.3.0
-
None
-
None
-
Unknown
Description
According to this question and answer on StackOverflow, 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.