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:

bin/standalone.sh -Djava.net.preferIPv4Stack=false

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), and note - IPv4-Compatible IPv6 Address are deprecated (see RFC 4291 section 2.5.1.1). 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:

12:59:31,222 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) Listening on localhost.localdomain/127.0.0.1:4447

even though it is bound and listening only on ::ffff:127.0.0.1:4447.