<br><font size=2 face="sans-serif">Trial and error for me as well, or maybe
we're both just slow :-)</font>
<br><font size=2 face="sans-serif"><br>
________________________<br>
Richard Kim<br>
Deutsche Bank Americas<br>
Global Banking, New York<br>
rich.kim@db.com<br>
P: +1 212.250.4984</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Tim Perrett <tperrett@googlemail.com></b>
</font>
<p><font size=1 face="sans-serif">05/18/2009 06:00 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">Rich Kim/db/dbcom@DBAmericas</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">RabbitMQ Discuss <rabbitmq-discuss@lists.rabbitmq.com>,
rabbitmq-discuss-bounces@lists.rabbitmq.com</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [rabbitmq-discuss] Fanout exchange
not playing ball?</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Thanks Richard - that was just the ticket.<br>
<br>
There does not appear to be a great deal of examples on this anywhere<br>
- is this the case or am I just being amazingly slow? ;-)<br>
<br>
Cheers, Tim<br>
<br>
On Mon, May 18, 2009 at 10:31 PM, Rich Kim <rich.kim@db.com> wrote:<br>
><br>
> Taking a stab at this one, but have you setup your two listening clients<br>
> with separate queue names? When using a fanout exchange and binding
queues<br>
> to the exchange, when you attach the second listener to the exchange,
the<br>
> queue name is already found, and therefore performs a NOOP. Both listeners<br>
> share the same queue name, and thereafter begin round-robin like behavior.<br>
><br>
> Create two listeners with distinct queue names, and you should see
your<br>
> expected behavior.<br>
><br>
> ________________________<br>
> Richard Kim<br>
> Deutsche Bank Americas<br>
> Global Banking, New York<br>
> rich.kim@db.com<br>
> P: +1 212.250.4984<br>
><br>
><br>
> Tim Perrett <tperrett@googlemail.com><br>
> Sent by: rabbitmq-discuss-bounces@lists.rabbitmq.com<br>
><br>
> 05/18/2009 05:27 PM<br>
><br>
> To<br>
> RabbitMQ Discuss <rabbitmq-discuss@lists.rabbitmq.com><br>
> cc<br>
> Subject<br>
> [rabbitmq-discuss] Fanout exchange not playing ball?<br>
><br>
><br>
><br>
><br>
> Hey guys,<br>
><br>
> I've setup a fanout exchange and my expectation does not match the<br>
> output... My expectation was that using a fanout exchange all<br>
> listening clients would get all messages - however this doesn't appear<br>
> to be the case. I started two separate instances of the same<br>
> application and run the listeners - I then publish a message into
the<br>
> exchange, and it appears that App1 gets a message, then App2 gets<br>
> nothing. I send another message into the queue and then App2 gets
the<br>
> message but not App1 - im a little lost how this could happen?<br>
><br>
> My creation code looks like:<br>
><br>
> val ticket = channel.accessRequest("/data")<br>
> channel.exchangeDeclare(ticket, "mult", "topic")<br>
> channel.queueDeclare(ticket, "mult_queue")<br>
> channel.queueBind(ticket, "mult_queue", "mult",
"example.*")<br>
> channel.basicConsume(ticket, "mult_queue",
false, new<br>
> SerializedConsumer(channel, this))<br>
><br>
><br>
> Any ideas / suggestions?<br>
><br>
> Cheers, Tim<br>
><br>
> _______________________________________________<br>
> rabbitmq-discuss mailing list<br>
> rabbitmq-discuss@lists.rabbitmq.com<br>
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss<br>
><br>
><br>
> ---<br>
> This communication may contain confidential and/or privileged information.<br>
> If you are not the intended recipient (or have received this communication<br>
> in error) please notify the sender immediately and destroy this<br>
> communication. Any unauthorized copying, disclosure or distribution
of the<br>
> material in this communication is strictly forbidden.<br>
><br>
> Deutsche Bank does not render legal or tax advice, and the information<br>
> contained in this communication should not be regarded as such.<br>
</font></tt>
<br>
<br>
<span style="font-family:'Arial',sans-serif; font-size:8pt; color:#000000">---</span><br>
<span style="font-family:'Courier New',monospace; font-size:10pt; color:#000000">This communication may contain confidential and/or privileged information.<br>
If you are not the intended recipient (or have received this communication<br>
in error) please notify the sender immediately and destroy this<br>
communication. Any unauthorized copying, disclosure or distribution of the<br>
material in this communication is strictly forbidden.<br>
<br>
Deutsche Bank does not render legal or tax advice, and the information<br>
contained in this communication should not be regarded as such.</span>