]
Brian Stansberry moved WFLY-533 to WFCORE-361:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-361 (was: WFLY-533)
Affects Version/s: (was: 8.0.0.Alpha1)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.Beta1
(was: 9.0.0.Beta1)
CLONE - Config XML with <interface ...><any-ipv4-address
/></interface> + -Djava.net.preferIPv4Stack=false produces binding to ANY address
(error)
--------------------------------------------------------------------------------------------------------------------------------------------------
Key: WFCORE-361
URL:
https://issues.jboss.org/browse/WFCORE-361
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Pavel Janousek
Assignee: Brian Stansberry
Fix For: 1.0.0.Beta1
The same situation is with every shipped and supported configuration/profile. As base for
my explanation I'm using standalone.xml. Standalone.xml declares xmlns as:
{code}
<server xmlns="urn:jboss:domain:1.3">
{code}
The real XSD file which defined elements is
jboss-eap-6.0/docs/schema/jboss-as-config_1_3.xsd.
The very common Linux system has implemented and enabled dualstack in these days. If we
instruct AS instance to bind to +any+ IPv4 address via {code}<interface
name="public">
<any-ipv4-address />
</interface>{code}
The real result is to bind running AS instance to +any+ IP address, not only in IPv4
address space but in IPv6 too!
With default setting (= -Djava.net.preferIPv4Stack=true), result is correct - it is bound
to ANY IPv4 addresses only.