[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-452) mod_cluster with WildFly reports 0.0.0.0 to the balancer

[Michal Babacek (JIRA)]

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

Michal Babacek updated MODCLUSTER-452:
--------------------------------------
    Fix Version/s: 1.3.1.Beta3


> mod_cluster with WildFly reports 0.0.0.0 to the balancer
> --------------------------------------------------------
>
>                 Key: MODCLUSTER-452
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-452
>             Project: mod_cluster
>          Issue Type: Bug
>          Components: Core & Container Integration (Java)
>    Affects Versions: 1.3.0.Final
>            Reporter: Michal Babacek
>            Assignee: Radoslav Husar
>             Fix For: 1.3.1.Beta3
>
>
> While I was working on [issue 138|https://github.com/modcluster/mod_cluster/issues/138] (MODCLUSTER-448), it came to my attention that one can't force EAP 6.4 Beta (jbossweb, mod_cluster 1.2.11) to send anything like {{ajp://0.0.0.0:8009}} to the balancer. If one sets the application server to bind to 0.0.0.0, mod_cluster core correctly guesses 127.0.0.1 and sends {{ajp:/127.0.0.1:8009}} to the balancer.
> On the contrary, WildFly goes only half way: it reports 127.0.0.1 in the log:
> {noformat}
> [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000012: default-server connector will use /127.0.0.1
> {noformat}
> and yet it sends 0.0.0.0 to the balancer:
> {noformat}
> Node localhost (ajp://0.0.0.0:8009):
> {noformat}
> Note the {{localhost}} string in place of properly generated UUID: MODCLUSTER-451.
> For some historical context, I suggest: MODCLUSTER-91 and MODCLUSTER-168



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)