[jboss-jira] [JBoss JIRA] Commented: (JGRP-951) Add in support for IPv6 to JGroups testsuite

[Richard Achmatowicz (JIRA)]

    [ https://jira.jboss.org/jira/browse/JGRP-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12484997#action_12484997 ] 

Richard Achmatowicz commented on JGRP-951:
------------------------------------------

Bela, 

One question. The updates I made to allow the 2.8 testsuite to use IPv6 addressses didn't address one issue in build.xml.  You call runtest as follows, for udp.xml:

<runtest testname.ext="udp" threadcount="10" parallel="tests" initial.mcast.addr="235.10.10.10" initial.mcast.port="25100" initial.tcp.port="25100" testng.xmlfile="testng-udp.xml" />

That is, you are hardcoding IPv4 values for initial.mcast.addr, and you are using different address ranges across the different targets (udp, tcp, udp-flush, ...)for some reason. This makes switching the testsuite from IPv4 to IPv6 rather difficult.

I would like to replace these hardcoded values by the system property ${jgroups.udp.mcast_addr} so that the value gets picked up from build.properties.  Same for the mcast_port.  Is this OK? 

There shouldn't be any need to use different ranges of mcast addresses when calling runtest as these are run in sequence anyway.



 

> Add in support for IPv6 to JGroups testsuite
> --------------------------------------------
>
>                 Key: JGRP-951
>                 URL: https://jira.jboss.org/jira/browse/JGRP-951
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Richard Achmatowicz
>            Assignee: Richard Achmatowicz
>            Priority: Minor
>             Fix For: 2.4, 2.6, 2.7, 2.8
>
>
> JGroups needs to support both IPv4 and IPv6. When running JGroups on a machine which has a dual IP stack, two system properties need to be set in order to specify preferences for one version of IP over the other:
> (excerpt from Sun notes) 
> 1. IPv6 stack is preferred by default, since on a dual-stack machine IPv6 socket can talk to both IPv4 and IPv6 peers.
> To change this, set -Djava.net.preferIPv4Stack=true  
> (NOTE: if we use java.net.preferIPv4Stack=true and use IPv6 addresses, we get a message  "exception while trying to create socket:java.net.SocketException: Protocol family unavailable")
> 2. By default, we would prefer IPv4 addresses over IPv6 addresses (i.e., when querying the name service (e.g., DNS service), we would return IPv4 addresses ahead of IPv6 addresses).
> There are two reasons for this choice:
>    1. There are some applications that expect an IPv4 address textual format, i.e. "%d.%d.%d.%d". Using an IPv4 address minimizes the surprises;
>    2. Using IPv4 address, we can use one call (with an IPv6 socket) to reach either a legacy IPv4-only service, or an IPv6 service (unless the IPv6 service is on a Ipv6 only node).
> To change this, set -Djava.net.preferIPv6Addresses=true 
> This issue concerns modifications to the JGroups testsuite to allow easy switching from IPv4 to IPv6 for testing purposes.
>  

-- 
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