jboss.messaging.controlchanneludpaddress and jboss.messaging.datachanneludpaddress do not correctly override the default values in the persistence file when running the testsuite. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1632 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1632 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP08 Reporter: Phillip Thurmond Assignee: Tim Fox Fix For: 1.4.0.SP3.CP09 I am running an example test from the JBM testsuite using the following command: ant -Dtest.bind.address=3ffe:ffff:0100:f101::1 -Djboss.messaging.datachanneludpport=45567 -Djboss.messaging.controlchanneludpport=45568 -Djboss.messaging.datachanneludpaddress=ff0e::1:2:3 -Djboss.messaging.controlchanneludpaddress=ff0e::1:2:3 -Dtest-mask=*FailoverNodeTest clustering-tests The ipv6 address 'ff0e::1:2:3' should be overriding the default values of '228.6.6.6' and '228.7.7.7' in the mysql-persistence-service.xml file. Instead, jgroups tries to use the default values as can be seen in this log snippet: 13:27:08,412 WARN @RMI TCP Connection(2)-127.0.1.1 [UDP] could not bind to /228.7.7.7 (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 This causes the several tests to fail. If I edit the mysql-persistence-service.xml and replace the default multicast addresses with 'ff0e::1:2:3', jgroups uses the correct addresses, and the test passes. -- 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