[
https://issues.apache.org/jira/browse/AMQ-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236997#comment-17236997
]
Thomas Lutz edited comment on AMQ-8018 at 11/22/20, 6:44 PM:
-------------------------------------------------------------
This is my Dockerfile:
[https://github.com/symptoma/activemq/blob/master/Dockerfile]
It downloads and runs ActiveMQ in Version 5.16.0.
To reproduce, clone: [https://github.com/symptoma/activemq]
Run
{{docker build -t symptoma/activemq .}}
followed by
{{docker run -it -p 61616:61616 -p 8161:8161 symptoma/activemq:latest}}
And afterwards try to access:
[http://127.0.0.1:8161/]
I get an ERR_EMPTY_RESPONSE here. Previous versions work perfectly fine (only
change is version number in the Dockerfile).
was (Author: tholu):
This is my Dockerfile:
[https://github.com/symptoma/activemq/blob/master/Dockerfile]
It downloads and runs ActiveMQ in Version 5.16.0.
To reproduce, clone: [https://github.com/symptoma/activemq]
Run
{{docker build -t symptoma/activemq .}}
followed by
{{docker run -it -p 61616:61616 -p 8161:8161 symptoma/activemq:latest}}
And afterwords try to access:
[http://127.0.0.1:8161/]
I get an ERR_EMPTY_RESPONSE here. Previous versions work perfectly fine (only
change is version number in the Dockerfile).
> 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)
