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

[Marek Goldmann]

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.

-- 
Marek Goldmann

JBoss by Red Hat