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

[Paul Ferraro (JIRA)]

     [ https://jira.jboss.org/jira/browse/MODCLUSTER-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro resolved MODCLUSTER-91.
------------------------------------

    Fix Version/s: 1.1.0.Beta1
                       (was: 1.1.0.CR1)
       Resolution: Done


Restored 1.0.x connector address defaulting logic - checking not only for undefined connector address, but also wildcard addresses.  This does not work well if proxies are auto-discovered (there may be no proxies at the time of initialization).  A better fix involves adding MCMPHandler.isEstablished(), which returns true only when a connection is established to a proxy, and the local address of the socket is known and the connector address is set.  ModClusterService should postpone sending any CONFIG messages, and any load factor calculation, until MCMPHandler.isEstablished() = true.  We should also investigate whether it is a good idea to associate an MCMPHandler with a single engine - so that the MCMPHandler can establish the connector address when appropriate.

> Connector bind address of 0.0.0.0 propagated to proxy
> -----------------------------------------------------
>
>                 Key: MODCLUSTER-91
>                 URL: https://jira.jboss.org/jira/browse/MODCLUSTER-91
>             Project: mod_cluster
>          Issue Type: Bug
>    Affects Versions: 1.0.1.GA
>            Reporter: Brian Stansberry
>            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 contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira