[
https://issues.jboss.org/browse/AS7-3783?page=com.atlassian.jira.plugin.s...
]
Pavel Janousek closed AS7-3783.
-------------------------------
Resolution: Done
We should force to ban 127.0.0.1 and IP alias name (as localhost) everywhere in source
base (code, config, property files etc.). About this problem there is another issue
already, hence I'm closing this one.
-Dipv6 should modify localhost to localhost6 everywhere too
-----------------------------------------------------------
Key: AS7-3783
URL:
https://issues.jboss.org/browse/AS7-3783
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.1.0.Final
Reporter: Pavel Janousek
Assignee: Shelly McGowan
Priority: Critical
Common installed Linux box has associated host name alias *localhost* to *127.0.0.1* and
*localhost6* to *::1*. When we specify -Dipv6 in maven invocation, we also might expect
doing appropriate changes in configurations etc.
But everywhere isn't user IP address as number (127.0.0.1) and even we specify
-D$node0=<something elese than 127.0.0.1>, some pieces of configs are still
associated with *localhost*.
In this case almost everything is associated to $node0 value, but something is still
associated to localhost. This is very bad especially in case of IPv6 testing, because
$node0 contains some IPv6 IP address (number either alias name format) but some elements
are bound to localhost (which is resolved as 127.0.0.1 usually).
I prefer to incorporate this behavior inside testsuite in case when mven is invoked with
-Dipv6 option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira