[jboss-jira] [JBoss JIRA] (AS7-3040) IPv6: IP address proccessing in pure IPv6 (only) network stack environment

IPv6: IP address proccessing in pure IPv6 (only) network stack environment -------------------------------------------------------------------------- Key: AS7-3040 URL: https://issues.jboss.org/browse/AS7-3040 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.Beta1b Reporter: Pavel Janousek Assignee: Jason Greene Priority: Blocker Attachments: IPv6-adresses.png Actual implementation of processing IP address (e.g. from XML cfg) as 127.0.0.1 is +totally+ useless in IPv6 environment (it has its own *incompatible* ekvivalent - _::1_). The default behavior of AS7 is IPv6 disabled at all, so user should be forced to *reconfigure* his instance of AS7 to run it in pure IPv6 network stack only (the are also missing some document described this process yet! - AS7-3039). So one issue is when AS7 instance is bring up with default configuration (distributed standalone.xml), but in an IPv6 network environment available only like: {code} bin/standalone.sh -Djava.net.preferIPv4Stack=false {code} It uses configured address 127.0.0.1 (default from standalone.xml if key _jboss.bind.address_ isn't defined) as binding point which it could try to use. It is bad and should be avoided, because 127.0.0.1 isn't +valid IPv6 address+, nor allowed IPv6 address format specification (see [RFC 5952|http://tools.ietf.org/html/rfc5952]), and note - IPv4-Compatible IPv6 Address are deprecated (see [RFC 4291 section 2.5.1.1|http://tools.ietf.org/html/rfc4291#section-2.5.5]). Only one possibility is allowed now - IPv4-Mapped IPv6 Address, but it has it's own format and regulary defined address space, also it doesn't make sense to use it in pure IPv6 environment. *So conclusion - a such address setting (127.0.0.1) in pure IPv6 environment is miss-configuration error at all and starting AS7 instance in this case should only report valid error message about what happens and end itself, not trying to do with a such address format anything - nor convert to other address format, nor use its own inside logic (convert to ::ffff:<IPv4>) etc..* This error relates to other one - produced log contains nonsense messages as:{code}12:59:31,222 INFO [org.jboss.as.remoting] (MSC service thread 1-2) Listening on localhost.localdomain/127.0.0.1:4447 {code} even though it is bound and listening only on _::ffff:127.0.0.1:4447_.