7.6.3. Verifying the ActiveMQ Configuration

MCollective can act in one of two ways: it can transport host-to-host messages, or it can broadcast messages with the appropriate hosts responding to the broadcasting host. In the latter case, a message that is broadcast has a "topic" that is used to indicate which hosts should respond.
After ActiveMQ has started, verify that it is listening for messages for the OpenShift Enterprise topics. It can take 60 seconds or longer for the activemq daemon to finish initializing and start answering queries.
Verify that authentication is working, replacing password with your password: 
# curl --head --user admin:password http://localhost:8161/admin/xml/topics.jsp
A 200 OK message should be displayed, followed by the remaining header lines. If you see a 401 Unauthorized message, it means your user name or password is incorrect.
Verify that the service returns a topic list, replacing password with your password: 
# curl --user admin:password --silent http://localhost:8161/admin/xml/topics.jsp | grep -A 4 topic
If no results are returned, run it again without the --silent argument, and without using grep to filter messages: 
# curl http://localhost:8161/admin/xml/topics.jsp
If the following message is returned, it means that either the ActiveMQ service is not running, or it has not finished initializing. 
curl: (7) couldn't connect to host
If this persists for more than 60 seconds, and the activemq daemon is running, look in the ActiveMQ log file: 
# more /var/log/activemq/activemq.log
After you have verified the ActiveMQ configuration, disable the unused Jetty by commenting out the line that loads jetty.xml. This can be done by editing activemq.xml manually or by running the following command: 
# sed -ie "s/\(.*import resource.*jetty.xml.*\)/<\!-- \1 -->/" /etc/activemq/activemq.xml
Restart the activemq service for the changes to take effect: 
# service activemq restart