[rabbitmq-discuss] Odd behavoiur with mcollective and RabbitMQ 3.1.3

Emile Joubert emile at rabbitmq.com
Fri Jul 19 11:58:40 BST 2013

Hi Niclas,

Thanks for reporting this issue.

On 19/07/13 08:09, Niclas Meier wrote:

> Fortunately I found an "old" 3.0.1 Rabbit MQ installation on one of our
> servers and on this version mcollecive works like before

Are you sure it actually used to work? After trying the same on RabbitMQ
3.0.1 I see on the STOMP port a SUBSCRIBE to
and a SEND to
The topics don't match so no message is delivered.
The "mco ping" command returns :

---- ping statistics ----
No responses received

That doesn't look like it's working to me. Tested with mcollective 2.2.4
and stomp gem 1.2.10.

> Additionally I have stuff like this in the sasl log:
> =SUPERVISOR REPORT==== 19-Jul-2013::07:57:23 ===
>      Supervisor: {<0.570.0>,rabbit_stomp_client_sup}
>      Context:    shutdown
>      Reason:     reached_max_restart_intensity

I don't see this. I see the same STOMP dialogue and the same failure to
match SUBSCRIBE and SEND topics. Is there anything in the regular broker
log, or any errors before the one you quoted?

The only changes to the RabbitMQ STOMP adapter since 3.0.1 was to relax
the rules about header values containing colons, changes to the way
"/reply-queue" is prefixed when using temporary destinations, neither of
which is relevant.

If you think the STOMP adapter is in violation of the spec then can you
supply a network packet trace of the interaction that I can replay to


More information about the rabbitmq-discuss mailing list