[jboss-jira] [JBoss JIRA] (AS7-4140) Change distributtion of -Dmcast through testsuite

[Richard Achmatowicz (JIRA)]

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

Richard Achmatowicz edited comment on AS7-4140 at 3/12/12 11:52 AM:
--------------------------------------------------------------------

We should already be able to use one multicast address (-Dmcast) as long as all of the multicast channels use different ports, which they do at the moment. I'm checking with Andy Taylor for the HornetQ configuration in standalone-full-ha.xml, as there are multicast addresses used there too which have been temporarily overlooked.

The way things work at the moment, you may specify -Dmcast, -Dmcast.jgroupsDiag and -Dmcast.modcluster. If you specify only -Dmcast, the remaining addresses use the value of -Dmcast.

I have tested:

1. loopback configuration

{noformat}
./integration-tests.sh -Dipv6
{noformat}

which assigns -Dnode=::1, -Dnode1=::1 and -Dmcast=ff01::1. To use this loopback-based configuration, you need to set a static multicast route on lo, using

{noformat}
# as sudo or root
# route -A inet6 add ff01::/32 dev lo
{noformat}

2. non-loopback configuration

{noformat}
./integration-tests.sh -Dnode0=<a global mcast address> -Dnode1=<another global mcast address> -Dmcast=<a global mcast address>

e.g.
./integration-tests.sh -Dnode0=<a global mcast address> -Dnode1=<another global mcast address> -Dmcast=ff0e::1
{noformat}

I did see an issue with this on Friday, but it may be local to my machine. This configuration should work for standalone.xml, standalone-full.xml and standalone-ha.xml. 

The configuration standalone-full-ha.xml needs some adjustment due to HornetQ mcast addresses as mentioned earlier.
                
      was (Author: rachmato):
    We should already be able to use one multicast address (-Dmcast) as long as all of the multicast channels use different ports, which they do at the moment. I'm checking with Andy Taylor for the HornetQ configuration in standalone-full-ha.xml, as there are multicast addresses used there too which have been temporarily overlooked.

The way things work at the moment, you may specify -Dmcast, -Dmcast.jgroupsDiag and -Dmcast.modcluster. If you specify only -Dmcast, the remaining addresses use the value of -Dmcast.

I have tested:

1. loopback configuration

{noformat}
./integration-tests.sh -Dipv6
{noformat}

which assigns -Dnode=::1, -Dnode1=::1 and -Dmcast=ff01::1. To use this loopback-based configuration, you need to set a static multicast route on lo, using

{noformat}
# as sudo or root
# route -A inet6 add ff01::/32 dev lo
{noformat}

2. non-loopback configuration

{noformat}
./integration-tests.sh -Dnode0=<a global mcast address> -Dnode1=<another global mcast address> -Dmcast=<a global mcast address>

e.g.
./integration-tests.sh -Dnode0=<a global mcast address> -Dnode1=<another global mcast address> -Dmcast=ff0e::1
{noformat}

I did see an issue with this on Friday, but it may be local to my mamchine. This configuration should work for standalone.xml, standalone-full.xml and standalone-ha.xml. 

The configuration standalone-full-ha.xml needs some adjustment due to HornetQ mcast addresses as mentioned earlier.
                  
> Change distributtion of -Dmcast through testsuite
> -------------------------------------------------
>
>                 Key: AS7-4140
>                 URL: https://issues.jboss.org/browse/AS7-4140
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Test Suite
>    Affects Versions: 7.1.1.Final
>            Reporter: Pavel Janousek
>            Assignee: Richard Achmatowicz
>            Priority: Blocker
>             Fix For: 7.1.2.Final
>
>
> Please change present behavior.
> We need to define only one property -Dmcast (for ex., the name doesn't matter now) as command line parameter - this multicast address is needed to be distributed to every subsystem which manages any multicast communication. It is needed to be unique in every subsystem - JGroups, HornetQ etc. because we must avoid to interfere each other => port assignation must be unique for every a such component.
> This change is needed in both - IPV4 and IPv6...

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