[
https://issues.jboss.org/browse/AS7-3786?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-3786:
-----------------------------------
A lot of progress has been made, although we still have few "localhost"
occurences.
Today I've sent an email with this list challenging people to fix.
Some TestCases are run against hard-coded 127.0.0.1
---------------------------------------------------
Key: AS7-3786
URL:
https://issues.jboss.org/browse/AS7-3786
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.1.0.Final
Reporter: Pavel Janousek
Assignee: Ondrej Zizka
Priority: Critical
Some TestCases are hard bound to *127.0.0.1* IP address. I think, it is useless -
especially testing in IPv6 environment is impossible in this case for a such
TestCase(-s).
These classes aren't in integration testsuite part, it is in other places.
Some of them are (maybe I've overlooked some others):
- org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase
- org.jboss.as.controller.test.RemoteChannelProxyControllerTestCase
- org.jboss.as.controller.test.RemoteProxyControllerProtocolTestCase
- org.jboss.as.controller.ModelControllerClientTestCase
- org.jboss.as.jmx.JMXSubsystemTestCase
- org.jboss.as.jmx.ModelControllerMBeanTestCase
Otherwise these tests are run *before* IP address transformation (usually used node0
variable and tranforms AS7 config file standalone-*.xml), so maybe there isn't present
now any mechanism how to get/propagate proper (and wanted) IP address.
Also note - some of them are hardcoded to IP name alias *localhost* - see JBPAPP-8132 for
localhost vs. localhost6.
--
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