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 retrieve the newest tag for an image?
  • How to remove all tags for a docker repository locally?
  • Mount Volume to Host
  • Scaling: Docker containers vs Vms
  • How to run the Google app engine server using Dockerfile
  • How to direct logs from etsy statsd docker to stdout?
  • [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.

  • docker maven plugin error
  • Cloudera cdh cluster docker deployment
  • Localhost connection refused in Docker development environment
  • SpringBoot @RestController not accessible from outside docker container
  • How do I create a database in the Postgres Docker container? [duplicate]
  • Docker for mac not starting after latest version upgrade Version 1.12.1 (build: 12133) 2d5b4d9c3daa089e3869e6355a47dd96dbf39856
  • 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.