[CAMEL-12111] Reconnect doesn't work if camel is started with rabbit broker initially inaccessible and automaticRecoveryEnabled=true or not set

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.20.1
• Fix Version/s: 2.20.2, 2.21.0
• Component/s: camel-rabbitmq
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Jeremy M Isikoff
• Created: 02/Jan/18 20:09
• Updated: 06/Jan/18 12:03
• Resolved: 06/Jan/18 12:03

Description

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.

Issue Links

• links to: GitHub Pull Request #2164
• links to: GitHub Pull Request #2164