Vaclav Bystricky created CAMEL-12229:
----------------------------------------
Summary: Some RabbitMQ channels are never started when target
queue doesn't exist during component startup
Key: CAMEL-12229
URL: https://issues.apache.org/jira/browse/CAMEL-12229
Project: Camel
Issue Type: Bug
Components: camel-rabbitmq
Affects Versions: 2.20.2
Reporter: Vaclav Bystricky
Commit 8311af003ab888ca53a042ce5e9955b7cd5a845b reveals previously hidden bug.
*Steps to reproduce*:
# configure rabbitmq consumer to connect to existing rabbitmq server but to
non existing queue Q1
# start rabbitmq consumer with several channels.
# after some time create Q1 on target rabbitmq server
*Expected result*:
All channels are connected to rabbitmq server and can consume messages from Q1
*Actual result*:
All channels are connected to rabbitmq server and but only one channel can
consume messages from Q1
Note:
Separation on channels creating and their starting causes that channels are not
started in reconnect loop if they were successfully created in createConsumer
but not started in startConsumers().
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
