[
https://issues.apache.org/jira/browse/AMQ-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17237002#comment-17237002
]
Jean-Baptiste Onofré commented on AMQ-8018:
-------------------------------------------
Did you try with 0.0.0.0 in conf/jetty.xml:
{code:java}
<bean id="jettyPort" class="org.apache.activemq.web.WebConsolePort"
init-method="start">
<!-- the default port number for the web console -->
<property name="host" value="0.0.0.0"/>
<property name="port" value="8161"/>
</bean> {code}
That's the difference between 5.15.13 and 5.16.0: for security reason, we
changed jetty to listen only on localhost, so it's not "accessible" from the
docker container.
So, just change to 0.0.0.0 in {{conf/jetty.xml}} (in your docker image) and it
will work.
> Web Console broken after upgrade to 5.16.0
> ------------------------------------------
>
> Key: AMQ-8018
> URL: https://issues.apache.org/jira/browse/AMQ-8018
> Project: ActiveMQ
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 5.16.0
> Environment: ActiveMQ is deployed in a Docker container with JDK8 and
> alpine, find the Dockerfile here to reproduce:
> [https://github.com/symptoma/activemq/blob/master/Dockerfile]
> Docker file is published here: [https://hub.docker.com/r/symptoma/activemq]
> Reporter: Thomas Lutz
> Assignee: Jean-Baptiste Onofré
> Priority: Major
>
> After upgrading to 5.16.0, the Web Console on port 8161 is no longer
> accessible for me, there is an empty response returned instead of the usual
> HTTP Basic Auth.
> The exact same configuration works perfectly fine in 5.15.13.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
