[jboss-jira] [JBoss JIRA] (AS7-3993) Fix up generation of IPv6-ready configs for IPv6 testing

[Richard Achmatowicz (JIRA)]

    [ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673748#comment-12673748 ] 

Richard Achmatowicz edited comment on AS7-3993 at 3/5/12 3:09 PM:
------------------------------------------------------------------

The configurations are still not being constructed correctly for me.
I pulled in your updates, saw the changes you made, and executed:

{noformat}
./integration-tests.sh clean install -Dipv6 -Dnode0=1:0:0:1::11 -Dnode1=1:0:0:1::12 -Dmcast=ff0e::1 -Dmcast.jgroupsDiag=ff0e::2 -Dmcast.modcluster=ff0e::3 -Dts.clust
{noformat}

The smoke configuration builds ok. The clustering configuration standalone-ha.xml loks like this:
{noformat}
    <interfaces>
        <interface name="management">
            <inet-address value="1:0:0:1::11"/>
        </interface>
        <interface name="public">
            <inet-address value="${jboss.bind.address:1:0:0:1::11}"/>
        </interface>
        <interface name="unsecure">
            <inet-address value="${jboss.bind.address.unsecure:1:0:0:1::11}"/>
        </interface>
    </interfaces>

    <socket-binding-group name="standard-sockets" default-interface="public" port-offset="0">
        <socket-binding name="management-native" interface="management" port="9999"/>
        <socket-binding name="management-http" interface="management" port="9990"/>
        <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>
        <socket-binding name="http" port="8080"/>
        <socket-binding name="https" port="8443"/>
        <socket-binding name="jgroups-diagnostics" port="0" multicast-address="224.0.75.75" multicast-port="7500"/>
        <socket-binding name="jgroups-mping" port="0" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45700"/>
        <socket-binding name="jgroups-tcp" port="7600"/>
        <socket-binding name="jgroups-tcp-fd" port="57600"/>
        <socket-binding name="jgroups-udp" port="55200" multicast-address="${jboss.default.multicast.address:ff0e::1}" multicast-port="45688"/>
        <socket-binding name="jgroups-udp-fd" port="54200"/>
        <socket-binding name="modcluster" port="0" multicast-address="224.0.1.105" multicast-port="23364"/>
        <socket-binding name="osgi-http" interface="management" port="8090"/>
        <socket-binding name="remoting" port="4447"/>
        <socket-binding name="txn-recovery-environment" port="4712"/>
        <socket-binding name="txn-status-manager" port="4713"/>
        <outbound-socket-binding name="mail-smtp">
            <remote-destination host="1:0:0:1::11" port="25"/>
        </outbound-socket-binding>
    </socket-binding-group>

{noformat}


                
      was (Author: rachmato):
    The configurations are still not being constructed correctly for me.
I pulled in your updates, saw the changes you made, and executed:

{noformat}
./integration-tests.sh clean install -Dipv6 -Dnode0=1:0:0:1::11 -Dnode1=1:0:0:1::12 -Dmcast=ff0e::1 -Dmcast.jgroupsDiag=ff0e::2 -Dmca.modcluster=ff0e::3 -Dts.clust
{noformat}

The smoke configuration builds ok. The clustering configuration standalone-ha.xml loks like this:
{noformat}
    <interfaces>
        <interface name="management">
            <inet-address value="1:0:0:1::11"/>
        </interface>
        <interface name="public">
            <inet-address value="${jboss.bind.address:1:0:0:1::11}"/>
        </interface>
        <interface name="unsecure">
            <inet-address value="${jboss.bind.address.unsecure:1:0:0:1::11}"/>
        </interface>
    </interfaces>

    <socket-binding-group name="standard-sockets" default-interface="public" port-offset="0">
        <socket-binding name="management-native" interface="management" port="9999"/>
        <socket-binding name="management-http" interface="management" port="9990"/>
        <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>
        <socket-binding name="http" port="8080"/>
        <socket-binding name="https" port="8443"/>
        <socket-binding name="jgroups-diagnostics" port="0" multicast-address="224.0.75.75" multicast-port="7500"/>
        <socket-binding name="jgroups-mping" port="0" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45700"/>
        <socket-binding name="jgroups-tcp" port="7600"/>
        <socket-binding name="jgroups-tcp-fd" port="57600"/>
        <socket-binding name="jgroups-udp" port="55200" multicast-address="${jboss.default.multicast.address:ff0e::1}" multicast-port="45688"/>
        <socket-binding name="jgroups-udp-fd" port="54200"/>
        <socket-binding name="modcluster" port="0" multicast-address="224.0.1.105" multicast-port="23364"/>
        <socket-binding name="osgi-http" interface="management" port="8090"/>
        <socket-binding name="remoting" port="4447"/>
        <socket-binding name="txn-recovery-environment" port="4712"/>
        <socket-binding name="txn-status-manager" port="4713"/>
        <outbound-socket-binding name="mail-smtp">
            <remote-destination host="1:0:0:1::11" port="25"/>
        </outbound-socket-binding>
    </socket-binding-group>

{noformat}


                  
> Fix up generation of IPv6-ready configs for IPv6 testing
> --------------------------------------------------------
>
>                 Key: AS7-3993
>                 URL: https://issues.jboss.org/browse/AS7-3993
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 7.1.0.Final
>            Reporter: Richard Achmatowicz
>            Assignee: Ondrej Zizka
>            Priority: Critical
>             Fix For: 7.1.1.Final
>
>
> The testsuite uses a combination of:
> - the ant script clustering-build.xml, with target build-clustering-udp
> - the ant script common-targets.xml, with target ts.config-as.ip-with-multicast and
> - the XSLT script changeIAddresses.xsl 
> to set up IPv6 addresses for testing multi-node tests.
> There are several problems:
> - the XSLT script is broken and does not change the multicast addresses
> - a number of multicast addresses are not receiving IPv6 defaults/overrides; in particular, we have the following required overrides:
> UDP JGroups stack multicast requirements: 
> -- socket-binding jgroups-udp: no IPv6 multicast address assigned, due to broken changeIPAddresses.xml   
> -- socket-binding jgroups-diagnostics: no IPv6 multicast address assigned, due to no parameter passed in ts.config-as.ip-with-multicast  
> TCP JGroups stack multicast-requirements:
> -- socket-binding jgroups-mping: no IPv6 multicast address assigned, due to no parameter passed in ts.config-as.ip-with-multicast   
> -- socket-binding jgroups-diagnostics: no IPv6 multicast address assigned, due to no parameter passed in ts.config-as.ip-with-multicast  
> mosdcluster multicast-requirements:    
> -- socket-binding modcluster: no IPv6 multicast address assigned, due to no parameter passed in ts.config-as.ip-with-multicast 
> This results in server configurations which are not correctly configured for testing against IPv6 addresses.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira