[rabbitmq-discuss] 3.0.1 STOMP bug - reply-to header

Toby Corkindale toby.corkindale at strategicdata.com.au
Thu Jan 31 06:01:10 GMT 2013

On 29/01/13 20:24, Matthias Radestock wrote:
> Toby,
> On 29/01/13 04:59, Toby Corkindale wrote:
>> On 22/12/12 02:36, Matthias Radestock wrote:
>>> On 21/12/12 00:41, Toby Corkindale wrote:
>>>> When testing against RabbitMQ 3.0.1, we're seeing what looks like a bug
>>>> and regression compared to the last 2.9 version.
>>>> The stomp adapter is turning a reply-to header for a topic queue into a
>>>> temp queue.
>>>> Eg, the reply queue name is getting munged from
>>>>    /topic/foo.export.pid    to  /reply-queue//topic/foo.export.pid
>>> This looks like an accidental side effect of the change we made to allow
>>> AMQP clients to handle reply-to headers created by stomp clients. Thanks
>>> for reporting this. I have filed a bug.
>> I wondered how this bug was going?
>> I [...] wondered if it'd been fixed and I'd just missed the release
>> announcement?
> It's been fixed but not released yet - 3.0.1, the version you were
> testing, is (still) the most recent rabbit release.
> If you don't want to wait until the next release you can try a nightly
> build - http://www.rabbitmq.com/nightly-builds.html

Thanks Matthias.
I've tested our app against the nightly build, and it now 
passes our tests that were failing before.


More information about the rabbitmq-discuss mailing list