Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-12111

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

    XMLWordPrintableJSON

    Details

    • 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
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      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.

        Attachments

          Activity

            People

            • Assignee:
              davsclaus Claus Ibsen
              Reporter:
              jisikoff Jeremy M Isikoff
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: