Maybe this is a problem on some specific OS / JVM combination?
As for most of the cases we know of it works.
On Fri, Jan 23, 2015 at 6:27 PM, Jason Greene <jason.greene(a)redhat.com>
wrote:
Huh?
-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.
> On Jan 23, 2015, at 11:18 AM, Phil Festoso <pfestoso(a)redhat.com> wrote:
>
> Hi all,
>
> 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/>.
>
>
> 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?
>
> Thanks.
>
> Phil Festoso
> Sr. Technical Account Manager, Global Support Services
> Red Hat, Inc.
> T: 312.612.0035
> E: philfest(a)redhat.com
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev