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

Some RabbitMQ channels are never started when target queue doesn't exist during component startup

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.20.2
    • Fix Version/s: 2.23.0
    • Component/s: camel-rabbitmq
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      Commit 8311af003ab888ca53a042ce5e9955b7cd5a845b reveals previously hidden bug.

      Steps to reproduce:

      1. configure rabbitmq consumer to connect to existing rabbitmq server but to non existing queue Q1
      2. start rabbitmq consumer with several channels.
      3. 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().

       

        Attachments

          Activity

            People

            • Assignee:
              davsclaus Claus Ibsen
              Reporter:
              vbystricky Vaclav Bystricky
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: