ActiveMQ within Wildfly on a Docker container gives: Invalid “host” value “0.0.0.0” detected

I have Wildfly running in a Docker container.
Within Wildfly the messaging-activemq subsystem is active.
The subsystem and extension defaults are taken from the standalone-full.xml file.

After starting wildfly, following output is displayed

  • How to get all containers using Dockerode and Javascript
  • How to pull docker image from docker hub private registry into Azure Container Service (ACS)?
  • Connect to Docker Machine remotely in Docker Toolbox
  • Which Official Docker Image(s) should I use for running an application with multiple dependencies?
  • boot2docker: what does poweroff do to all my docker containers?
  • Azure - Docker : Remote error : bad certificate :
  • [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool -- 64)
    AMQ121005: Invalid "host" value "0.0.0.0" detected for "http-connector" connector.
    Switching to "eeb79399d447".
    If this new address is incorrect please manually configure the connector to use the proper one.
    

    The eeb79399d447 is the docker container id.
    It’s also impossible to connect to jms from my java client. While connecting it gives the following error.

    AMQ214016: Failed to create netty connection: java.net.UnknownHostException: eeb79399d447
    

    When I start wildfly on my local workstation (outside docker) the problem does not occur and I can connect to jms and send my messages.

  • Rich editors in a Docker development environment
  • How to make postgresql database connectable from outside of the postgres docker container?
  • Can't figure out how I have to build my Docker architecture
  • Restrict access to docker swarm (manager / configuration)
  • Sidekiq jobs aren't firing in development mode, only in production
  • Can't find Docker data volume on host
  • One Solution collect form web for “ActiveMQ within Wildfly on a Docker container gives: Invalid “host” value “0.0.0.0” detected”

    You need to edit the standalone-full.xml to cope with jms behind NAT and when you run the docker container pass though the ip and port that your jms client can use to connect, which is the ip of the machine running docker in Dockers’ default config

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.