Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-9057

Pausing any address blocks the SF queue / cluster forwarding for all addresses

XMLWordPrintable

    • 1
    • False
    • None
    • False
    • Hide

      Configure 2 or more brokers in a load-balancing cluster (message-load-balancing=ON_DEMAND for cluster connection, redistributon-delay=0 for catch-all address).

      Start consumers (preferably ones with a throttled consume rate) on multiple addresses on one broker.

      Start producers (with a higher production rate than the consumers) on the opposite broker for the same addresses.

      Wait for a little bit of message backlog to occur.

      Pause one address on the broker where the producer is / was connected

      We see a backlog develop in the SF queue and delivery to the consumer on the other broker remains blocked, even after all the messages on the consumer broker are consumed.

      Show
      Configure 2 or more brokers in a load-balancing cluster (message-load-balancing=ON_DEMAND for cluster connection, redistributon-delay=0 for catch-all address). Start consumers (preferably ones with a throttled consume rate) on multiple addresses on one broker. Start producers (with a higher production rate than the consumers) on the opposite broker for the same addresses. Wait for a little bit of message backlog to occur. Pause one address on the broker where the producer is / was connected We see a backlog develop in the SF queue and delivery to the consumer on the other broker remains blocked, even after all the messages on the consumer broker are consumed.

      If any address on a clustered broker with redistribution enabled is paused, messages stop flowing through the sf queue and forwarding is effectively blocked for all addresses.

       

              gaohoward Howard Gao
              rhn-support-dhawkins Duane Hawkins
              Tiago Bueno Tiago Bueno
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: