On 01/31/2016 10:19 PM, jjw tectec wrote:
I sent out the email more than 3 days ago, but it's still not appearing
in the mailing list. Has it been deleted from the archive?

I got the mail, but not the attached image. I actually thought I had replied as well, but it appears not...

On Thu, Jan 28, 2016 at 1:02 PM, jjw tectec <[email protected]
<mailto:[email protected]>> wrote:

    I've set up a simple 4-broker system, where between Bs (source
    broker) and Bd (destination broker) are two middle brokers set up in
    parallel, like this:

    Inline image 1

    The script that I used to set up all the resources & routes is shown
    at the end of this message.
    I attached a publisher to Bs and attached 3 subscribers to the other
    3 brokers.
    What I was expecting to see was all 3 brokers should see messages.
    The actual observation was: Only B1 and Bf received messages. B2
    never received messages, even when B1 was down.

    route map showed that all broker connections were set up as
    expected, but why would only the first route work and not the other?
    (I have added more brokers B3 B4... into the test, always, only the
    first established route would work.) Please help.

Without the picture I'm not entirely sure I'm correctly understanding your system. However it sounds like it may be the fact that messages from a queue are not broadcast to all subscribers; the consumers compete for the messages and each message goes to only one of them.

For small numbers of messages the same consumer may end up getting them all. For larger numbers there should normally be more fair balancing. You can improve the balance a little with the --ack option to qpid-route (which controls the acking frequency and also prefetch).

To use queue routes with a fanout, you would need to create and bind a queue for each downstream broker. E.g.


B1->Exchange
    |
    |-> queue1     ---------> B2->Exchange
    |-> queue2     ---
                     |
                     |------> B3->Exchange

etc


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to