Thanks for the quick reply Simon.<br><br>While I was hoping it was just something I'd messed up, I'm still glad that it's a known issue and that there are plans to resolve it. In the short term I believe we're OK living with this behavior.<br>
<br>Matt<br><br><div class="gmail_quote">On Thu, Sep 13, 2012 at 4:06 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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.<br>
<br>
Cheers, Simon<div><div class="h5"><br>
<br>
On 12/09/12 23:57, Matt Pietrek wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
I'm using federation with a topic exchange between two RabbitMQ nodes.<br>
As part of this, I've defined an exchange, 'skytap' which is a topic<br>
exchange (yes, I know it's not *really* a topic exchange).<br>
<br>
The upstream sets for the skytap exchange are pointed to each other, as<br>
described in the Federation doc as a "Pair of federated exchanges". For<br>
routing keys, I'm using something of the form "foo.XXX", where XXX is<br>
either 'east' or 'west'.<br>
<br>
On server 'A', I have a queue 'foo' bound to the skytap exchange, using<br>
a routing key of 'foo.west'. On server 'B', I have a queue 'foo' bound<br>
to the skytap exchange, using a routing key of 'foo.east'.<br>
<br>
This all generally works as expected. In particular, I have a client app<br>
running on server 'A' that publishes using the 'foo.west' routing key.<br>
In other words, everything should be happening locally to server 'A'.<br>
<br>
However, via the Management Web UI, I'm noticing that there seems to be<br>
message traffic to server 'B'. In particular, on the Exchanges tab for<br>
server 'B' if I select the 'skytap' exchange, I see:<br>
<br>
Channel � � � � � � � � � � � � � � � � �| publish �| confirm<br>
<rabbit@xxx.3.299.0> (1) � � � | 20/s � � �| 20/s<br>
<br>
However (as I'd expect), no messages go into the 'foo' queue (or any<br>
other queue) on server 'B'. Likewise, on the queue tab of server 'A',<br>
the queue named "skytap -> rabbit@serverA.blah.blah", shows<br>
incoming/deliver/ack rates of 20/s as well.<br>
<br>
This runs counter to what I'd expect from reading the Federation doc,<br>
specifically: "Therefore the federated exchange only receives messages<br>
for which it has a subscription."<br>
<br>
Am I misunderstanding something, or perhaps don't have things configured<br>
optimally?<br>
<br>
Thanks,<br>
<br>
Matt<br>
<br>
<br>
<br>
<br>
<br></div></div>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><span class="HOEnZb"><font color="#888888"><br>
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</font></span></blockquote></div><br>