[rabbitmq-discuss] Problems getting reply_to to work
buck.robert.j at gmail.com
Sun Sep 30 13:56:47 BST 2012
Yes, "immediate" was cribbed from the sample code, as was much of the code
I put together, well, at least the concepts were cribbed that is.
So I should yank immediate? Or is there an alternate thing I should do?
I am not sure why 'response_queue.subscribe' doesn't trigger the setting of
the name. It's rather weird in that regard, neither the client nor the
server see the generated queue name. I would be guessing that the Ruby amqp
gem is broken in this regard?
On Sun, Sep 30, 2012 at 3:18 AM, Matthias Radestock
<matthias at rabbitmq.com>wrote:
> On 30/09/12 06:49, Michael Klishin wrote:
>> 2012/9/29 Bob Buck <buck.robert.j at gmail.com
>> <mailto:buck.robert.j at gmail.**com <buck.robert.j at gmail.com>>>
>> I get no message response, and at the server the metadata.reply_to is
>> an empty string ??? (even though in the management console I see
>> something like "amq.gen-**wVDstTQg3NTbQVTjfqcDuO".
>> Just for the record, the question was answered on the amqp gem mailing
> Interesting. Why doesn't the 'response_queue.subscribe' trigger the
> setting of the name?
> As an aside, there is a spurious "immediate => true" in the
> exchange.publish. I hope that isn't cribbed from some example code, since
> we are dropping support for 'immediate' in the next major rabbit release.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss