[rabbitmq-discuss] ReplyTo / ReplyToAddress fail to betransferred

[Steven Taylor]

possible cause... prior to adopting the rabbit url-style format for queue
identification

e.g. exhangeType://exchange/routing.key

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.




On 18 January 2012 12:55, Emile Joubert <emile at rabbitmq.com> wrote:

> Hi Steven,
>
> On 18/01/12 12:34, Steven Taylor wrote:
> > I tried with publication address which is there for convenience method
> > if I remember correctly and also reply-to.  The info just isn't turning
> > up in the subscriber.  It is set successfully in the publisher.  No
> > exceptions.
>
> To solve this issue can you supply a minimal example that exhibits the
> faulty behaviour?
>
> Another useful diagnostic aid is to connect to the broker via the
> protocol tracer, or to observe the network traffic with Wireshark (which
> has an AMQP protocol analyser). This will confirm whether the producer,
> broker or consumer are at fault.
>
>
>
> -Emile
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120121/acd41ce0/attachment.htm>