[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-294) Connector bind address of 0.0.0.0 propagated to proxy

[Lami Akagwu (JIRA)]

Lami Akagwu created MODCLUSTER-294:
--------------------------------------

             Summary: Connector bind address of 0.0.0.0 propagated to proxy
                 Key: MODCLUSTER-294
                 URL: https://issues.jboss.org/browse/MODCLUSTER-294
             Project: mod_cluster
          Issue Type: Bug
    Affects Versions: 1.0.1.GA
            Reporter: Lami Akagwu
            Assignee: Paul Ferraro
             Fix For: 1.1.0.Beta1


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.

The java side needs to understand that 0.0.0.0 is useless as a client address and send something useful.  Trick is deciding what's useful.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira