Menu
I installed ActiveMQ 5.5.0 on my Windows machine, and it had a web console (http://localhost:8161/admin) working out of the box.
Then I installed ActiveMQ (same version) on a remote Linux box (IP: AAA.BBB.CCC.DDD), but whenever I point the browser to
http://AAA.BBB.CCC.DDD:8161/admin
I get the "Unable to connect" error in the browser.
The network connection is there, I can connect to AAA.BBB.CCC.DDD via ssh and to another web application running on the same server.
Therefore I think that the cause of the problem is wrong configuration of the embedded Jetty server of ActiveMQ.
How can fix the problem, i. e. enable the access to the web console from a remote browser?
842
You can monitor ActiveMQ using the Web Console by pointing your browser at http://localhost:8161/admin . From ActiveMQ 5.8 onwards the web apps is secured out of the box. The default username and password is admin/admin. You can configure this in the conf/jetty-real.
Sending a message to an ActiveMQ Queue is very simple: you have to open the ActiveMQ Admin Console in the Web Browser using a link like http://HOSTNAME:8161/admin/index.jsp : Notes: 1) The default password for the ActiveMQ admin user is admin. 2) In real life, the messages are sent by different applications/ servers.
In your ActiveMQ config file you should see something like:
<import resource="${activemq.base}/conf/jetty.xml"/>
This starts up an embedded Jetty container with the web console.
If you start the broker on the console, you should see the following if everything works
INFO | ActiveMQ WebConsole initialized.
INFO | Initializing Spring FrameworkServlet 'dispatcher'
INFO | ActiveMQ Console at http://0.0.0.0:8161/admin
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
