[infinispan-issues] [JBoss JIRA] Commented: (ISPN-98) Switch test suite to use MPING instead of TCPPING for the tcp stack

[ https://jira.jboss.org/jira/browse/ISPN-98?page=com.atlassian.jira.plugin... ] Galder Zamarreno commented on ISPN-98: -------------------------------------- So, we know that hudson show failures when using MPING but having run the testsuite in cluster10 (the slave used by Hudson) several times, the failures do not always happen. When they happen, you see stuff like this in the logs in spite of java.net.preferIpv4Stack = true: 2009-07-16 03:55:28,030 WARN [org.jgroups.protocols.MPING] (pool-1-thread-5) could not bind to /228.10.10.16 (IPv4 address); make sure your mcast_addr is of the same type as the IP stack (IPv4 or IPv6). Will ignore mcast_addr, but this may lead to cross talking (see http://www.jboss.com/wiki/Edit.jsp?page=CrossTalking for details). Exception was: java.net.BindException: Cannot assign requested address I'm trying to get TRACE on org.jgroups when it fails but no luck so far. Having compared good logs against bad logs generated in cluster10, I see the following appearing *only* when the tests fail: 2009-07-16 03:55:28,153 WARN [org.jgroups.protocols.TCP] (pool-1-thread-4) failed to join /224.0.75.75:7500 on eth2: java.net.SocketException: No such device Not sure if this is somehow cause or consequence though. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira