Hi Ken,
Thank you for your reply.
My problem is with the default exchange, the server receives a queue
from the other broker in the replyTo field with no exchange defined.
Thank you,
Regards.
On Sex, 2013-02-01 at 10:43 -0500, Ken Giusti wrote:
> Hi Bruno,
>
> Since federation routes are uni-directional, you'd need to create another
> route to get from b2 back to b1 for the response.
>
> Here's a simple example using the 'drain' and 'spout' clients:
>
> If I have two brokers:
>
> qpidd --auth no -p 8888
> qpidd --auth no -p 9999
>
> And set up two routes, one in each direction:
>
> qpid-route dynamic add 127.0.0.1:9999 127.0.0.1:8888 amq.direct
> qpid-route dynamic add 127.0.0.1:8888 127.0.0.1:9999 amq.direct
>
> Then, from different consoles I can send replies and responses:
>
> (from 8888 ---> 9999)
> ./drain -f -b 127.0.0.1:9999 "amq.direct/request; {create:always}"
> ./spout -b 127.0.0.1:8888 --content "FOO" "amq.direct/request"
>
> (from 9999 ---> 8888)
> ./drain -f -b 127.0.0.1:8888 "amq.direct/response; {create:always}"
> ./spout -b 127.0.0.1:9999 --content "FOO" "amq.direct/response"
>
>
> -K
>
> ----- Original Message -----
> > Hi,
> >
> > Imagine that I have two brokers, b1 and b2 that have a federation
> > link
> > witch sends every message from b1 amq.direct exchange to b2. b1 has a
> > client connected that sends a request to amq.direct/requests with
> > replyTo set to his local queue. b2 has a server connected that
> > listens
> > for requests in amq.direct/requests. The server receives the request,
> > is
> > it possible to send the reply to b1 queue as set in message replyTo
> > property? If not, any suggestion to accomplish this?
> >
> > Thank you.
> >
> > --
> > Bruno Matos
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
--
Bruno Matos
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
