[
https://issues.jboss.org/browse/AS7-3786?page=com.atlassian.jira.plugin.s...
]
Pavel Janousek commented on AS7-3786:
-------------------------------------
Ondrej,
yes there are still there...:-(
As you could see
[
there|https://hudson.qa.jboss.com/hudson/job/AS7-TS-linux-experiments/3/c...], recent
master contains for ex. org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase,
org.jboss.as.controller.test.RemoteProxyControllerProtocolTestCase or
org.jboss.as.controller.test.RemoteChannelProxyControllerTestCase still bound directly to
127.0.0.1 although the run is invoked as:{code}./build.sh clean install
-Dmaven.test.failure.ignore -Dskip-download-sources -U -B -fae -DallTests
-Dnode0=10.16.95.7 -Dnode1=10.16.95.8 -DudpGroup=227.43.89.216{code}
Mentioned Jenkins job (AS7-TS-linux-experiments) is used by mine as reference for
comparing what is related to IPv6 only and what is general issue with some bad approach
and not using specified (wanted) IP address(-es).
Some non-Arquillian 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: Pavel Janousek
Priority: Critical
Fix For: 7.1.1.Final
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