You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2018/03/09 08:19:00 UTC
[jira] [Updated] (CAMEL-12229) Some RabbitMQ channels are never
started when target queue doesn't exist during component startup
[ https://issues.apache.org/jira/browse/CAMEL-12229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-12229:
--------------------------------
Fix Version/s: (was: 2.21.0)
2.21.1
> 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
> Priority: Minor
> Fix For: 2.20.3, 2.21.1
>
>
> 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)