[rabbitmq-discuss] Unintended message flow using federation?

Simon MacMullen simon at rabbitmq.com
Thu Sep 13 12:06:45 BST 2012

Hi Matt. This is a limitation in the federation binding logic that we've 
recently noticed - bindings get transmitted "too far" upstream. We're 
hoping to get it fixed in the next major release.

Cheers, Simon

On 12/09/12 23:57, Matt Pietrek wrote:
> I'm using federation with a topic exchange between two RabbitMQ nodes.
> As part of this, I've defined an exchange, 'skytap' which is a topic
> exchange (yes, I know it's not *really* a topic exchange).
> The upstream sets for the skytap exchange are pointed to each other, as
> described in the Federation doc as a "Pair of federated exchanges". For
> routing keys, I'm using something of the form "foo.XXX", where XXX is
> either 'east' or 'west'.
> On server 'A', I have a queue 'foo' bound to the skytap exchange, using
> a routing key of 'foo.west'. On server 'B', I have a queue 'foo' bound
> to the skytap exchange, using a routing key of 'foo.east'.
> This all generally works as expected. In particular, I have a client app
> running on server 'A' that publishes using the 'foo.west' routing key.
> In other words, everything should be happening locally to server 'A'.
> However, via the Management Web UI, I'm noticing that there seems to be
> message traffic to server 'B'. In particular, on the Exchanges tab for
> server 'B' if I select the 'skytap' exchange, I see:
> Channel                                  | publish  | confirm
> <rabbit at xxx.3.299.0> (1)       | 20/s      | 20/s
> However (as I'd expect), no messages go into the 'foo' queue (or any
> other queue) on server 'B'. Likewise, on the queue tab of server 'A',
> the queue named "skytap -> rabbit at serverA.blah.blah", shows
> incoming/deliver/ack rates of 20/s as well.
> This runs counter to what I'd expect from reading the Federation doc,
> specifically: "Therefore the federated exchange only receives messages
> for which it has a subscription."
> Am I misunderstanding something, or perhaps don't have things configured
> optimally?
> Thanks,
> Matt
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

Simon MacMullen
RabbitMQ, VMware

More information about the rabbitmq-discuss mailing list