camel-rabbitmq component causes a connection leak when there is an error during declaration of exchanges/queues (e.g. when an exchange with the same name but different type already exists).
Problem lies in org.apache.camel.component.rabbitmq.RabbitConsumer:
if declareExchangeAndQueue gets called, and if it throws an exception (e.g. because the exchange is already declared with different configuration) the exception is caught and consumed in the constructor, and the channel is never closed. I think the exception should be propagated in this case, because it is not recoverable (or at least there should be an option for this). It would also cause the app startup to fail, which would be a good thing in this case.