<div>possible cause... prior to adopting the rabbit url-style format for queue identification</div><div>�</div><div>e.g.�exhangeType://exchange/routing.key</div><div>�</div><div>I was using "exchange::routing.key" in the reply-to property.� *Perhaps* the rabbit client got intollerant of my naming scheme while I wasn't looking.� Not sure.� It is working now.� Just thought I'd email this note as a follow up.</div>
<div>�</div><div><br><br>�</div><div class="gmail_quote">On 18 January 2012 12:55, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
Hi Steven,<br>
<div class="im"><br>
On 18/01/12 12:34, Steven Taylor wrote:<br>
> I tried with publication address which is there for convenience method<br>
> if I remember correctly and also reply-to. �The info just isn't turning<br>
> up in the subscriber. �It is set successfully in the publisher. �No<br>
> exceptions.<br>
<br>
</div>To solve this issue can you supply a minimal example that exhibits the<br>
faulty behaviour?<br>
<br>
Another useful diagnostic aid is to connect to the broker via the<br>
protocol tracer, or to observe the network traffic with Wireshark (which<br>
has an AMQP protocol analyser). This will confirm whether the producer,<br>
broker or consumer are at fault.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
-Emile<br>
</font></span></blockquote></div><br>