[infinispan-dev] JGroups 2.8 and Infinispan

[Bela Ban]

Ah yep, that's something we have to consider, but maybe that's a change 
in the test harness code

Mircea Markus wrote:
> Bela Ban wrote:
>> For you information: in 2.8, we're attempting to find out whether 
>> you're running an IPv6-only stack and accordingly provide a default 
>> IPv6 multicast address. The opposite of course for IPv4-only stacks. 
>> The problematic case is duplex stacks, which is unfortunately the 
>> majority of all setups...
> Not sure that would work for parallel tests harness, as it parses the 
> xml confing and changes the IP address in order to assure different 
> clusters won't see each others. So if  the address defaults to same 
> value for all threads in the suite, clusters will conflict.
>>
>> In other words, even if you forget the system property above, you 
>> should be fine in 2.8... hopefully... :-)
>>
>> Mircea Markus wrote:
>>> The issue was the one pointed out.
>>> Cause was that "java.net.preferIpv4Stack" does not get propagated  
>>> from  property *parent\pom.xml* to the JVM running the tests.
>>> This is rather strange, as all other property do get propagated 
>>> correctly. Anyone encountered anything similar before?
>>> The fix/hack was to enforce "java.net.preferIpv4Stack" 
>>> programatical;y, in an @BeforeSuite. This sorted the problem.
>>>
>>>
>>>
>>> Bela Ban wrote:
>>>> What stack were you running on (IPv4 or IPv6) ? If it is IPv6 
>>>> *only*, then 230.8.8.8 is *not* a valid multicast address !
>>>>
>>>> If you have a dual stack, use -Djava.net.preferIpv4Stack=true to 
>>>> get IPv4 (then the mcast_addr is correct) or 
>>>> -Djava.net.preferIPv6Addresses=true and change the mcast_addr to a 
>>>> valid IPv6 address
>>>>
>>>> Mircea Markus wrote:
>>>>> It doesn't work on linux:
>>>>> 2009-06-11 11:28:40,026 WARN  [org.jgroups.protocols.MPING] 
>>>>> (pool-1-thread-4) could not bind to /228.10.10.15 (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
>>>>>
>>>>> Here is my config:
>>>>>   <MPING bind_addr="127.0.0.1" break_on_coord_rsp="true"
>>>>>          mcast_addr="230.8.8.8" mcast_port="17890" ip_ttl="2"
>>>>>          num_initial_members="3"/>
>>>>>
>>>>> Any ideas?
>>>>
>>>
>>
>

-- 
Bela Ban
Lead JGroups / Clustering Team
JBoss - a division of Red Hat