Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-268

Incorrect/unpredicated PriorityBackup behavior when used with 2 broker vs 3 broker network.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Done
    • 7.1.0.fuse-046
    • JBoss A-MQ 6.0
    • None
    • None

    Description

      In a Standalone Fuse MQ broker (5.7) If a 2 Broker network is created using static network connector uri and a consumer is connected with failover URI like| failover:(tcp://localhost:61616,tcp://localhost:62616)?randomize=false&priorityBackup=true|

      once failover happens from Broker1 to Broker2 and Broker1 comes back again the consumer is switched from Broker2 to Broker1 even if broker2 doesn't go down.

      In a 3 broker netowrk with similar uri| failover:(tcp://localhost:61616,tcp://localhost:62616,tcp://localhost:63616)?randomize=false&priorityBackup=true|

      if failover happens from broker1 to broker2 and broker1 comes back online the consumer is not reconnected to broker1 however if Broker2 goes down it tries to failover to broker3 and quickly go back to broker1 which is priority broker.

      As per priority broker docs it should reconnect to broker1 after first failover and subsequent restart of broker1 (priority broker).

      Attachments

        Activity

          People

            dejanbosanac Dejan Bosanac (Inactive)
            ubhole Ulhas Bhole (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: