[rabbitmq-discuss] Pub/sub with expiring reply queue

Ben Hood 0x6e6562 at gmail.com
Wed Oct 29 13:36:36 GMT 2008


On Wed, Oct 29, 2008 at 11:10 AM, Richard Marr <richard.marr at gmail.com> wrote:

> The demo I've built delivers each message to two queues, but is
> currently syncronous so only waits for the first response. My debug
> output tells me that both subscribers (one per queue) get the message
> body intact, but the replyTo property is null, even though the reply
> queue name generated in the client looks valid. I put debug just
> before the RpcClient.publish() call in the RpcClient.primitiveCall()
> method and it lookeds fine.
> Should the properties object be passed through transparently?

Are you saying that when you debug the processRequest() method in the
server, that the replyTo field of the request propertiesis null when
after this line is executed:

AMQP.BasicProperties requestProperties = request.getProperties();



More information about the rabbitmq-discuss mailing list