Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Received-SPF: error (athena.apache.org: local policy)
Message-ID: <54BF5EF8.70501@nanthrax.net>
Date: Wed, 21 Jan 2015 09:10:32 +0100
From: =?UTF-8?B?SmVhbi1CYXB0aXN0ZSBPbm9mcsOp?= <jb@nanthrax.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: dev@karaf.apache.org
Subject: Re: [VOTE] Apache Karaf Cellar 3.0.1 release
References: <54BD0C3D.3020105@nanthrax.net>
	<OFF97669FA.51F6AC27-ONC1257DD3.002AD156-C1257DD3.002AD826@kisters.de>
	<CAD0r13fCMzT9OcGLKXn6pDPm8u88oeWFy5jpcKkQBuJseaFaZw@mail.gmail.com>
	<54BF457C.2080603@nanthrax.net>	<54BF4893.6060906@nanthrax.net>
	<CAD0r13eRMupy9=tOva=bA9MpYtDpG0XdD857-L2S5ad9kr4ojw@mail.gmail.com>
	<54BF5CD7.8010705@nanthrax.net>
 <CAD0r13e2MeeuCK6KUVtku_piB+wY0OX_0nxq+MotAcL85_s2+A@mail.gmail.com>
In-Reply-To: 
 <CAD0r13e2MeeuCK6KUVtku_piB+wY0OX_0nxq+MotAcL85_s2+A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Yes, but previously we use both: multicast AND tcp-ip. So even if it=20
didn't work in multicast, it uses tcp-ip. So maybe your interface never=20
worked with multicast ;)
Now, this config is no more possible: it's multicast OR tcp-ip.

Can you test the tcp-ip config ?

Regards
JB

On 01/21/2015 09:05 AM, Achim Nierbeck wrote:
> Strange, I didn't change anything on my Mac network interface. So we ne=
ed
> to file a bug at hazelcast then?
>
> Regards, Achim
>
> sent from mobile device
> Am 21.01.2015 09:02 schrieb "Jean-Baptiste Onofr=C3=A9" <jb@nanthrax.ne=
t>:
>
>> yes and no: it's a change in Hazelcast. So what would you propose:
>> 1/ disabling multicast and enable tcp-ip: in that case, it's a regress=
ion
>> for user using multicast on different machines. It will work in your c=
ase
>> for node on a single machine without multicast support on the interfac=
e (by
>> the way, it's the config used in hazelcast module tests as the tests r=
un on
>> a single machine)
>> 2/ enabling multicast and disable tcp-ip: it's the current case, it wo=
rks
>> for users on different machines using multicast, not when multicast is=
 not
>> allowed.
>>
>> So ...
>>
>> I would prefer the current situation (which works if your network
>> interface supports multicast).
>>
>> Regards
>> JB
>>
>> On 01/21/2015 08:51 AM, Achim Nierbeck wrote:
>>
>>> Hi,
>>> As it used to work without this tweak before it's still a regression.=
 :-)
>>>
>>> Regards, Achim
>>>
>>> sent from mobile device
>>> Am 21.01.2015 07:36 schrieb "Jean-Baptiste Onofr=C3=A9" <jb@nanthrax.=
net>:
>>>
>>>   It seems that I reproduce the same behavior by disable promisc/mult=
icast
>>>> on my network interface. Just disabling multicast and enabling tcp-i=
p in
>>>> etc/hazelcast.xml fixes the problem.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 01/21/2015 07:21 AM, Jean-Baptiste Onofr=C3=A9 wrote:
>>>>
>>>>   Ahhhh I may know.
>>>>>
>>>>> In previous Hazelcast version, it was possible to enable multicast =
AND
>>>>> tcp-ip for joining. Since Hazelcast 3.3.x, it's no more possible.
>>>>> By default, in the Cellar etc/hazelcast.xml, I enabled multicast an=
d
>>>>> disable tcp-ip.
>>>>>
>>>>> If your interface or network doesn't support multicast, it will fai=
l to
>>>>> discover the nodes.
>>>>>
>>>>> Can you try to change to tcp-ip (with localhost) instead of multica=
st ?
>>>>>
>>>>> Thanks,
>>>>> Regards
>>>>> JB
>>>>>
>>>>> On 01/21/2015 12:15 AM, Achim Nierbeck wrote:
>>>>>
>>>>>   Config seed port is 5701 and cluster size is 1. Some of the ports=
 seem
>>>>>> occupied!
>>>>>>
>>>>>>
>>>>>
>>>>>   --
>>>> Jean-Baptiste Onofr=C3=A9
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>
>> --
>> Jean-Baptiste Onofr=C3=A9
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>

--=20
Jean-Baptiste Onofr=C3=A9
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com