[mod_cluster-dev] 503 error when JBoss is bound to 0.0.0.0

[Brian Stansberry]

Yeah, that's a bug for sure. 
https://jira.jboss.org/jira/browse/MODCLUSTER-91

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 
unreachable.

Marek Goldmann wrote:
> I'm encountered a strange error. When I bind JBoss instance to 0.0.0.0  
> 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  
> (0.0.0.0)
> [Fri Aug 07 03:21:25 2009] [error] proxy: ajp: disabled connection for  
> (0.0.0.0)
> 
> This looks like a bug for me, because many administrators are binding  
> JBoss to 0.0.0.0.
> 


-- 
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat