I'm attempting to invoke an rpc using RabbitTemplate.convertSendAndReceive as the client and amqp_rpc_server as the server. The convertSendAndReceive is using the two parameter signature, and the appropriate handle_info/2 callback is being invoked properly.
The problem I'm encountering is that the reply queue that's created by the RabbitTemplate seems to only exist for an extremely short period of time. The response's basic publish's 'mandatory' property is set to 'true', which yields a 312, NO_ROUTE result.
I've stepped through the code w/ a debugger while simultaneously observing the RabbitMQ Management browser display and the queue does in fact appear. However, once the client request message has been sent, it seemingly nukes.
If it makes any difference, the rpc client's thread that invokes the initial request is part from an ExecutorService.
Any thoughts on why the reply queue's lifespan is so short? Has anyone else attempted polyglot rpc in this way?