ActiveMQ 5.6 em Debian 7.8 para Mcollective 2.0

Em um recente projeto eu tive que subir o ActiveMQ 5.6.x em Debian 7.8 para servir como fila para o Mcollective 2.0. Confesso que eu e sofri um pouco, mas compartilho o resultado para evitar sofrimento desnecessário dos colegas que desejem subir um cenário similar.

Vamos lá, aos corajosos quem forem instalar o ActiveMQ 5.6.x no Debian 7.8 para uso do Mcollective 2.0, segue abaixo o arquivo de configuração activemq.xml que funciona nessa combinação de OS/Middleware/Orquestrador.

    Licensed to the Apache Software Foundation (ASF) under one or more
    contributor license agreements.  See the NOTICE file distributed with
    this work for additional information regarding copyright ownership.
    The ASF licenses this file to You under the Apache License, Version 2.0
    (the "License"); you may not use this file except in compliance with
    the License.  You may obtain a copy of the License at

    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.

    <!-- Allows us to use system properties as variables in this configuration file -->
    <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>

    <broker xmlns=""

            Configure message persistence for the broker. The default persistence
            mechanism is the KahaDB store (identified by the kahaDB tag).
            For more information, see:

            <kahaDB directory="${activemq.base}/data/kahadb"/>

            The transport connectors expose ActiveMQ over a given protocol to
            clients and other brokers. For more information, see:


          <authenticationUser username="mcollective" password="marionette" groups="mcollective,everyone"/>
          <authenticationUser username="admin" password="secret" groups="mcollective,admins,everyone"/>
                  <authorizationEntry queue=">" write="admins" read="admins" admin="admins" />
                  <authorizationEntry topic=">" write="admins" read="admins" admin="admins" />
                  <authorizationEntry topic="mcollective.>" write="mcollective" read="mcollective" admin="mcollective" />
                  <authorizationEntry queue="mcollective.>" write="mcollective" read="mcollective" admin="mcollective" />
                    The advisory topics are part of ActiveMQ, and all users need access to them.
                    The "everyone" group is not special; you need to ensure every user is a member.
                  <authorizationEntry topic="ActiveMQ.Advisory.>" read="everyone" write="everyone" admin="everyone"/>

            <transportConnector name="openwire" uri="tcp://"/>
            <transportConnector name="stomp+nio" uri="stomp+nio://"/>



Com essa configuração, o Mcollective 2.0 de vocês conseguirá se conectar no ActiveMQ 5.6 sem maiores dificuldades.