[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-91) Connector bind address of 0.0.0.0 propagated to proxy
Michal Babacek (JIRA)
issues at jboss.org
Fri Aug 8 06:29:01 EDT 2014
[ https://issues.jboss.org/browse/MODCLUSTER-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michal Babacek closed MODCLUSTER-91.
------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> Connector bind address of 0.0.0.0 propagated to proxy
> -----------------------------------------------------
>
> Key: MODCLUSTER-91
> URL: https://issues.jboss.org/browse/MODCLUSTER-91
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> 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 was sent by Atlassian JIRA
(v6.2.6#6264)
More information about the mod_cluster-issues
mailing list