<div dir="ltr">Just mentioned it as in mac osx when you start standalone-ha.xml with -b 0.0.0.0 <br>jgroups complains about not being able to bind and you get some ugly warning / error.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 23, 2015 at 6:32 PM, Jason Greene <span dir="ltr"><<a href="mailto:jason.greene@redhat.com" target="_blank">jason.greene@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Well our configuration for all releases of AS7, EAP and WildFly specifies:<br>
<br>
<interface name="public"><br>
<inet-address value="${jboss.bind.address:127.0.0.1}"/><br>
</interface><br>
<br>
So unless 127.0.0.1 was somehow bound to a non-loopback interface I don’t think that is even possible.<br>
<div class="HOEnZb"><div class="h5"><br>
> On Jan 23, 2015, at 11:28 AM, Tomaž Cerar <<a href="mailto:tomaz.cerar@gmail.com">tomaz.cerar@gmail.com</a>> wrote:<br>
><br>
> Maybe this is a problem on some specific OS / JVM combination?<br>
><br>
> As for most of the cases we know of it works.<br>
><br>
><br>
> On Fri, Jan 23, 2015 at 6:27 PM, Jason Greene <<a href="mailto:jason.greene@redhat.com">jason.greene@redhat.com</a>> wrote:<br>
> Huh?<br>
><br>
> -b does work, and the default is now loopback. The only thing that is really different is that we have a -b for the application ports and a -bmanagement for management ports.<br>
><br>
><br>
> > On Jan 23, 2015, at 11:18 AM, Phil Festoso <<a href="mailto:pfestoso@redhat.com">pfestoso@redhat.com</a>> wrote:<br>
> ><br>
> > Hi all,<br>
> ><br>
> > One of the changes from EAP 5 to 6 is that the -b option no longer "just works" and requires the admin to change the configuration to use <loopback-address/> instead of <inet-address/>.<br>
> ><br>
> ><br>
> > Some of my customers were surprised by the change. They enjoyed the ease of use that -b gave them and are hoping to see that feature brought back. I noticed that in WF 8.2 -b does just work (at least on the RHEL vms I tested). Does this mean that users can expect to see -b back in play (ie w/o need for config changes) for EAP 7?<br>
> ><br>
> > Thanks.<br>
> ><br>
> > Phil Festoso<br>
> > Sr. Technical Account Manager, Global Support Services<br>
> > Red Hat, Inc.<br>
> > T: <a href="tel:312.612.0035" value="+13126120035">312.612.0035</a><br>
> > E: <a href="mailto:philfest@redhat.com">philfest@redhat.com</a><br>
> ><br>
> > _______________________________________________<br>
> > wildfly-dev mailing list<br>
> > <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
><br>
> --<br>
> Jason T. Greene<br>
> WildFly Lead / JBoss EAP Platform Architect<br>
> JBoss, a division of Red Hat<br>
><br>
><br>
> _______________________________________________<br>
> wildfly-dev mailing list<br>
> <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
><br>
<br>
--<br>
Jason T. Greene<br>
WildFly Lead / JBoss EAP Platform Architect<br>
JBoss, a division of Red Hat<br>
<br>
</div></div></blockquote></div><br></div>