[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz reassigned AS7-3993: ---------------------------------------- Assignee: Ondrej Zizka (was: Richard Achmatowicz) -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz updated AS7-3993: ------------------------------------- Description: 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 was: 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 single and 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 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz updated AS7-3993: ------------------------------------- Summary: Fix up generation of IPv6-ready configs for IPv6 testing (was: Fix up generation of IPv6 ready configs for IPv6 testing) Description: 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. was: 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 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-3993: ----------------------------------- Richard, on the description, there is a list of problems. Since I don't know what the defaults should be. I need a list of changes needed, or better, the desired resulting state. Could you please write down such list? Thanks. -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-3993: ----------------------------------- To be clear what I need: The best would be the config file as it should be if the testsuite harness worked correctly. I will diff that file and do the changes. -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Radoslav Husar reassigned AS7-3993: ----------------------------------- Assignee: Radoslav Husar (was: Ondrej Zizka) Stuart fixed the core problem and I am now able to run the TS using IPv6. I am looking at logs now to see where the problems are. Tracking current failures here AS7-4006 -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz edited comment on AS7-3993 at 3/2/12 10:05 AM: ------------------------------------------------------------------- Ondra Stuart has fixed the problem with the changeIPAddresses.xsl script not updating any of the multicast address changes. Taking my comments above, here is what the section of the configuration file should look like: {noformat} <subsystem xmlns="urn:jboss:domain:webservices:1.1"> <modify-wsdl-address>true</modify-wsdl-address> <wsdl-host>::1</wsdl-host> <endpoint-config name="Standard-Endpoint-Config"/> [snip] </subsystem> </profile> <interfaces> <interface name="management"> <inet-address value="::1"/> </interface> <interface name="public"> <inet-address value="::1"/> </interface> <interface name="unsecure"> <inet-address value="::1"/> </interface> </interfaces> <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/> <socket-binding name="management-http" interface="management" port="${jboss.management.http.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="ff0e::1" multicast-port="7500"/> <socket-binding name="jgroups-mping" port="0" multicast-address="ff0e::2" 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="ff0e::3" multicast-port="45688"/> <socket-binding name="jgroups-udp-fd" port="54200"/> <socket-binding name="modcluster" port="0" multicast-address="ff0e::4" 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="localhost" port="25"/> </outbound-socket-binding> </socket-binding-group> {noformat} This is using a bind address of ::1 and different multicast addresses for jgroups-diagnostics (ff0e::1), jgroups-mping (ff0e::2), jgroups-udp(ff0e::3) and moscluster (ff0e::4). These are example values only and should be replaced by the variables representing those values passed into changeIPAddresses (e.g. udpMcastAddress, mpingMcastAddress, etc) Also, fix the wsdl-host as above, setti8ng it to the bind address (node0 in the testsuite for the fist node, or node1 for the second node). It would also be nice to have the mechanism know when we are using an IPv6 stack vs an IPv4 stack (e.g. check -Dipv6) and use IPv4 defaults or IPv6 defaults for the parameters as required, so if values are not passed in, a good set of defaults is used. was (Author: rachmato): Ondra Stuart has fixed the problem with the changeIPAddresses.xsl script not updating any of the multicast address changes. Taking my comments above, here is what the section of the configuration file should look like: {noformat} <subsystem xmlns="urn:jboss:domain:webservices:1.1"> <modify-wsdl-address>true</modify-wsdl-address> <wsdl-host>::1</wsdl-host> <endpoint-config name="Standard-Endpoint-Config"/> [snip] </subsystem> </profile> <interfaces> <interface name="management"> <inet-address value="::1"/> </interface> <interface name="public"> <inet-address value="::1"/> </interface> <interface name="unsecure"> <inet-address value="::1"/> </interface> </interfaces> <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/> <socket-binding name="management-http" interface="management" port="${jboss.management.http.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="ff0e::1" multicast-port="7500"/> <socket-binding name="jgroups-mping" port="0" multicast-address="ff0e::2" multicast-="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="ff0e::3" multicast-port="45688"/> <socket-binding name="jgroups-udp-fd" port="54200"/> <socket-binding name="modcluster" port="0" multicast-address="ff0e::4" 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="localhost" port="25"/> </outbound-socket-binding> </socket-binding-group> {noformat} This is using a bind address of ::1 and different multicast addresses for jgroups-diagnostics (ff0e::1), jgroups-mping (ff0e::2), jgroups-udp(ff0e::3) and moscluster (ff0e::4). These are example values only and should be replaced by the variables representing those values passed into changeIPAddresses (e.g. udpMcastAddress, mpingMcastAddress, etc) Also, fix the wsdl-host as above, setti8ng it to the bind address (node0 in the testsuite for the fist node, or node1 for the second node). It would also be nice to have the mechanism know when we are using an IPv6 stack vs an IPv4 stack (e.g. check -Dipv6) and use IPv4 defaults or IPv6 defaults for the parameters as required, so if values are not passed in, a good set of defaults is used. -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz edited comment on AS7-3993 at 3/2/12 10:37 AM: ------------------------------------------------------------------- In the short term, if all the multicast addresses are set to the value of udpGroup, this will be provide all with a reasonable default. But in the longer term, we need to be able to set each individually. Well, this in fact is not true. The diagnostics mcast address and the udp mcast address must be different. was (Author: rachmato): In the short term, if all the multicast addresses are set to the value of udpGroup, this will be provide all with a reasonable default. But in the longer term, we need to be able to set each individually. -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-3993: ------------------------------------------ Now for some reason, i've got three servers being constructed: - jbossas-clustering-udp-0 - jboss-as-clustering-udp-0-jdbc-store - jboss-as-clustering-udp-1 and the first two are being started, and the tests are consequently failing. This is when I execute: ./integration-tests.sh clean install -Dipv6 -Dnode0=1:0:0:1::11 -Dnode1=1:0:0:1::12 -DudpGroup=ff0e::1 -Dts.clust -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-3993: ----------------------------------- JGroups socket binding is in build/src/main/resources/configuration/subsystems/jgroups.xml -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-3993: ----------------------------------- The config now ends up like this: {code} <interfaces> <interface name="management"> <inet-address value="::1"/> </interface> <interface name="public"> <inet-address value="${jboss.bind.address:::1}"/> </interface> <!-- TODO - only show this if the jacorb subsystem is added --> <interface name="unsecure"> <!-- ~ Used for IIOP sockets in the standard configuration. ~ To secure JacORB you need to setup SSL --> <inet-address value="${jboss.bind.address.unsecure:::1}"/> </interface> </interfaces> <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/> <socket-binding name="management-http" interface="management" port="${jboss.management.http.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="jacorb" interface="unsecure" port="3528"/> <socket-binding name="jacorb-ssl" interface="unsecure" port="3529"/> <socket-binding name="jgroups-diagnostics" port="0" multicast-address="ff01::2" multicast-port="7500"/> <socket-binding name="jgroups-mping" port="0" multicast-address="${jboss.default.multicast.address:ff01::1}" 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:ff01::1}" multicast-port="45688"/> <socket-binding name="jgroups-udp-fd" port="54200"/> <socket-binding name="messaging" port="5445"/> <socket-binding name="messaging-throughput" port="5455"/> <socket-binding name="modcluster" port="0" multicast-address="ff01::3" 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" port="25"/> </outbound-socket-binding> </socket-binding-group> </server> {code} So this is fixed, but I still see failures in clustering, so what next? -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-3993: ------------------------------------- Damn, here is one related problem that needs fixing too ;-( https://issues.jboss.org/browse/AS7-4006?focusedCommentId=12673625&pa... -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-3993: ------------------------------------------ Creating substitutions like: {noformat} multicast-address="${jboss.default.multicast.address:ff01::1}" {noformat} is risky - the colon(:) is a token separator in these expressions. How do you know parsing is going to get the right tokens? I would enclose the IPv6 address in square brackets and test that substitution works correctly. -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-3993: ----------------------------------- Appearantly, it works - AS gets whatever is after the first colon. And I asked someone, I think Brian. I'll check with him. -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Radoslav Husar edited comment on AS7-3993 at 3/5/12 11:50 AM: -------------------------------------------------------------- If I run this with {code}mvn clean install -Dts.noSmoke -Dts.clust -Dipv6 -Dnode0=::1 -Dnode1=::1 -DudpGroup=ff02::1{code} I am getting {noformat}16:07:57,408 SEVERE [org.jgroups.protocols.UDP] (Timer-4,<ADDR>) failed sending message to cluster (67 bytes): java.lang.Exception: dest=/ff02:0:0:0:0:0:0:1:45688 (70 bytes), cause: java.io.IOException: Network is unreachable{noformat} was (Author: rhusar): If I run this with {code}mvn clean install -Dts.noSmoke -Dts.clust -Dipv6 -Dnode0=::1 -Dnode1=::2 -DudpGroup=ff02::1{code} I am getting {noformat}16:07:57,408 SEVERE [org.jgroups.protocols.UDP] (Timer-4,<ADDR>) failed sending message to cluster (67 bytes): java.lang.Exception: dest=/ff02:0:0:0:0:0:0:1:45688 (70 bytes), cause: java.io.IOException: Network is unreachable{noformat} -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-3993: ----------------------------------- Forgot to mention - the properties in that pull request are: {code:xml} <!-- IP address defaults. --> <node0>127.0.0.1</node0> <node1>127.0.0.1</node1> <mcast>230.0.0.4</mcast> <!-- Default multicast address. --> <mcast.jgroupsDiag>224.0.75.75</mcast.jgroupsDiag> <!-- for <socket-binding name="jgroups-diagnostics" .../> --> <mcast.modcluster >224.0.1.105</mcast.modcluster> <!-- for <socket-binding name="modcluster" .../> --> ... <!-- IPv6. AS7-2228. --> <profile> <id>ts.ipv6</id> <activation><property><name>ipv6</name></property></activation> <properties> <jvm.args.ip>-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true</jvm.args.ip> <!-- Override IPv4 defaults from the top. --> <node0>::1</node0> <node1>::1</node1> <mcast >ff01::1</mcast> <!-- ff01::1 is IPv6 Node-Local scope mcast addr. --> <mcast.jgroupsDiag>ff01::2</mcast.jgroupsDiag> <mcast.modcluster >ff01::3</mcast.modcluster> </properties> </profile> {code} -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka edited comment on AS7-3993 at 3/5/12 1:43 PM: ----------------------------------------------------------- Brian: {quote} The way the AS code works should be fine. The expression parser proceeds character by character from left to right. Once it enters an expression (i.e. sees '$' followed by '\{') it treats the first ':' as delimiting the system property from the default and it is not considered to be part of the default. Thereafter as it parses the default, it pays no particular attention to any character until it sees '}'. https://github.com/jbossas/jboss-dmr/blob/master/src/main/java/org/jboss/... Recommending that people add a special delimiter sounds like something that will introduce bugs, since it requires any code that may want to read the value to deal with the []. That said, I think in practice if people do use ${jboss.bind.address:[::1]} it will work fine, at least in the "interface" elements. The value ends up getting passed to InetAddress.getByName() which will handle the [] just fine. {quote} was (Author: ozizka): Brian: {quote} The way the AS code works should be fine. The expression parser proceeds character by character from left to right. Once it enters an expression (i.e. sees '$' followed by '{') it treats the first ':' as delimiting the system property from the default and it is not considered to be part of the default. Thereafter as it parses the default, it pays no particular attention to any character until it sees '}'. https://github.com/jbossas/jboss-dmr/blob/master/src/main/java/org/jboss/... Recommending that people add a special delimiter sounds like something that will introduce bugs, since it requires any code that may want to read the value to deal with the []. That said, I think in practice if people do use ${jboss.bind.address:[::1]} it will work fine, at least in the "interface" elements. The value ends up getting passed to InetAddress.getByName() which will handle the [] just fine. {quote} -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] 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} -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on AS7-3993: ------------------------------------- With regard to why the clustering tests are not working when bound to ::1 I think the loopback adaptor does not support multicast on linux. I needed to change the binding to a non-loopback interface for it to work. -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-3993: ----------------------------------- Ouch. I think we are getting hit by that stupid AntRun issue: http://jira.codehaus.org/browse/MANTRUN-172 - Properties passed to Maven as -D don't get passed to <ant> invocations when a profile sets the same property -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka reopened AS7-3993: ------------------------------- -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka updated AS7-3993: ------------------------------ Attachment: tmp-AS7-3993.zip Attaching configs I got by running {code} ./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 -Dts.noSmoke {code} -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-3993: ------------------------------------- I an now happy with how things work (without 1710). See my comment here for what are the requirements to run: https://issues.jboss.org/browse/AS7-4006?focusedCommentId=12673967&pa... Is everyone happy with that? -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-3993: ----------------------------------- Sorry guys, I am getting lost in all your happiness. Could you please clearly state what features of the testsuite harness you want in and which not? -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-3993: ------------------------------------- I check myself, TS runs OK and configs are generated OK besides jgroups-mping and jgroups-udp are the same by default -- could this a problem Richard? -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-3993: ------------------------------------------ Obviously, my point #3 is wrong - we can have udp and tcp stacks running at the same time; for example, with clustering using a UDP stack and messaging using a TCP stack. -- 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

[ https://issues.jboss.org/browse/AS7-3993?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-3993: ------------------------------------- @Ondra, different ports is not an option, some OSes treat it incorrectly. -- 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