Yeah, that's a bug for sure.
The java side needs to test if the InetAddress.isAnyLocalAddress() ==
true and if so provide something useful to the proxy.
Tricky thing is determining what's useful. An analysis of all
NetworkInterfaces and all InetAddresses associated with them and then
providing all of those to the proxy matches the meaning of '0.0.0.0'.
But from a load balancing point of view, there's only one server. Plus
the list is likely to include things like loopback addresses that the
proxy can't reach, but you don't want the proxy to mark the server as in
error, exclude it from load balancing, just because some interfaces are
Marek Goldmann wrote:
I'm encountered a strange error. When I bind JBoss instance to
address instead of a fixed ethernet address, node gets registered in
mod_cluster, shows in mod_cluster-manager, but every request to
registered contexts throws 503 error.
httpd error log:
[Fri Aug 07 03:21:05 2009] [error] (111)Connection refused: proxy:
ajp: attempt to connect to 0.0.0.0:8009 (0.0.0.0) failed
[Fri Aug 07 03:21:05 2009] [error] ap_proxy_connect_backend disabling
worker for (0.0.0.0)
[Fri Aug 07 03:21:15 2009] [error] proxy: ajp: disabled connection for
[Fri Aug 07 03:21:25 2009] [error] proxy: ajp: disabled connection for
This looks like a bug for me, because many administrators are binding
JBoss to 0.0.0.0.
Lead, AS Clustering
JBoss by Red Hat