Details
-
Bug
-
Resolution: Done
-
Blocker
-
7.1.1.Final
-
None
Description
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 TS passed, but I also reconfigure my machine to avoid IPv4 name address translation like:
#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
I've got this result:
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
It seems there are several other problems in clustering and domain, but I'll report them after deeper investigation.
