camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-12111) Reconnect doesn't work if camel is started with rabbit broker initially inaccessible and automaticRecoveryEnabled=true or not set
Date Sat, 06 Jan 2018 12:04:00 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-12111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-12111.
---------------------------------
    Resolution: Fixed
      Assignee: Claus Ibsen

Thanks for reporting and the PR

> Reconnect doesn't work if camel is started with rabbit broker initially inaccessible
and automaticRecoveryEnabled=true or not set
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-12111
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12111
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-rabbitmq
>    Affects Versions: 2.20.1
>            Reporter: Jeremy M Isikoff
>            Assignee: Claus Ibsen
>             Fix For: 2.20.2, 2.21.0
>
>
> Starting a camel rabbit consumer with the rabbitmq broker down and then bringing the
broker up used to work before 2.20.1 with automaticRecoveryEnabled=true.  
> The logic added in line 298 of the RabbitConsumer and line 301 now only will recover
in the case if automaticRecoveryEnabled=false by allowing it through to line 303 and opening
a connection for the FIRST TIME.  
>  In addition line 298 null pointers on '&& null' if automaticRecoveryEnabled
wasn't specified at all.
> https://github.com/apache/camel/blob/bad9ed4bb2ce1e258039d96ac80c71a746b0520d/components/camel-rabbitmq/src/main/java/org/apache/camel/component/rabbitmq/RabbitConsumer.java#L298
> As of now you can not have automaticRecoveryEnabled either not set or true and handle
have camel work in the startup with broker down and then up use case.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message