Yet another place where hardcoded IPv4 address scheme is used ------------------------------------------------------------- Key: AS7-3973 URL: https://issues.jboss.org/browse/AS7-3973 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.1.Final Reporter: Pavel Janousek Assignee: Ondrej Zizka Priority: Blocker Fix For: 7.1.1.Final After the last Stuart commit and merge to upstream (on -Thursday- Wednesday morning CET time zone), there are still some places where hardcoded IPv4 address scheme is used. Wrong TestCases are: - org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase - org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase Both of them use 127.0.0.1 directly even -Dnode0=::1 - it seems to be some other magic inside them because [there|http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-t...] TS passed, but I also reconfigure my machine to avoid IPv4 name address translation like: {code} #127.0.0.1 localhost.localdomain #127.0.0.1 pjanouse.brq.redhat.com localhost ::1 localhost6.localdomain6 localhost6 localhost ::1 pjanouse.brq.redhat.com localhost 127.0.0.2 both ::2 both 2001:0000:1234:0000:0000:c1c0:abcd:0876 ip6 {code} I've got this result:{code} Tests in error: org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out {code} It seems there are several other problems in clustering and domain, but I'll report them after deeper investigation.