-
1. Re: How to avoid warning "Invalid "host" value "0.0.0.0" detected for "http-connector" connector."?
msystems Dec 26, 2018 12:11 PM (in response to lafr)1 of 1 people found this helpfulTo get rid of the warning message, I created a new socket-binding and http-listener.
E.g.:
<subsystem xmlns="urn:jboss:domain:messaging-activemq:5.0">
...
...
<http-connector name="http-connector" socket-binding="activemq" endpoint="http-acceptor"/>
<http-connector name="http-connector-throughput" socket-binding="activemq" endpoint="http-acceptor-throughput">
...
...
<http-acceptor name="http-acceptor" http-listener="activemq"/>
<http-acceptor name="http-acceptor-throughput" http-listener="activemq">
...
...
</subsystem>
<subsystem xmlns="urn:jboss:domain:undertow:8.0" default-server="default-server" default-virtual-host="default-host" default-servlet-container="default" default-security-domain="other">
...
...
<http-listener name="activemq" socket-binding="activemq" enable-http2="true"/>
...
...
</subsystem>
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
...
...
<socket-binding name="activemq" interface="private" port="${jboss.activemq.port:8081}"/>
...
...
</subsystem>
As you can see, the socket-binding binds to the private interface and port 8081.
It works for me :-)
-
2. Re: How to avoid warning "Invalid "host" value "0.0.0.0" detected for "http-connector" connector."?
boris59 Jul 12, 2019 10:11 AM (in response to msystems)OK, while this helped me understand that I have a remote connector for JMS that I don't use (and hence now removed completely), isn't the original warning message (and action by ActiveMQ) wrong? Why is it OK for e.g. Undertow to listen on all interfaces but not for ActiveMQ? What if I want to do that?