이 콘텐츠는 선택한 언어로 제공되지 않습니다.

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.jspcurl --head --user admin:password http://localhost:8161/admin/xml/topics.jspcurl --head --user admin:password http://localhost:8161/admin/xml/topics.jsp
Copy to Clipboard Toggle word wrap
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# curl --user admin:password --silent http://localhost:8161/admin/xml/topics.jsp | grep -A 4 topic# curl --user admin:password --silent http://localhost:8161/admin/xml/topics.jsp | grep -A 4 topic
Copy to Clipboard Toggle word wrap
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
Copy to Clipboard Toggle word wrap
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
Copy to Clipboard Toggle word wrap
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
Copy to Clipboard Toggle word wrap
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
Copy to Clipboard Toggle word wrap
Restart the activemq service for the changes to take effect:
# service activemq restart
Copy to Clipboard Toggle word wrap
맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat