You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2015/01/19 14:53:01 UTC
[VOTE] Apache Karaf Cellar 3.0.1 release
Hi all,
I submit Apache Karaf Cellar 3.0.1 release to your vote.
Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12327148
Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1019/
Git tag:
cellar-3.0.1
Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Do not approve the release (please provide specific comments)
This vote will be open for 72 hours.
Thanks,
Regards
JB
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Andreas Pieber <an...@gmail.com>.
+1 (binding)
Kind regards,
Andreas
On Thu Jan 22 2015 at 6:35:22 PM Jamie G. <ja...@gmail.com> wrote:
> +1 (binding)
>
> Cheers,
> Jamie
>
> On Wed, Jan 21, 2015 at 5:09 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
> > +1 (binding)
> >
> > Regards
> > JB
> >
> >
> > On 01/19/2015 02:53 PM, Jean-Baptiste Onofré wrote:
> >>
> >> Hi all,
> >>
> >> I submit Apache Karaf Cellar 3.0.1 release to your vote.
> >>
> >> Release Notes:
> >>
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12311140&version=12327148
> >>
> >>
> >> Staging Repository:
> >> https://repository.apache.org/content/repositories/orgapachekaraf-1019/
> >>
> >> Git tag:
> >> cellar-3.0.1
> >>
> >> Please vote to approve this release:
> >>
> >> [ ] +1 Approve the release
> >> [ ] -1 Do not approve the release (please provide specific comments)
> >>
> >> This vote will be open for 72 hours.
> >>
> >> Thanks,
> >> Regards
> >> JB
> >
> >
> > --
> > Jean-Baptiste Onofré
> > jbonofre@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by "Jamie G." <ja...@gmail.com>.
+1 (binding)
Cheers,
Jamie
On Wed, Jan 21, 2015 at 5:09 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> +1 (binding)
>
> Regards
> JB
>
>
> On 01/19/2015 02:53 PM, Jean-Baptiste Onofré wrote:
>>
>> Hi all,
>>
>> I submit Apache Karaf Cellar 3.0.1 release to your vote.
>>
>> Release Notes:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12327148
>>
>>
>> Staging Repository:
>> https://repository.apache.org/content/repositories/orgapachekaraf-1019/
>>
>> Git tag:
>> cellar-3.0.1
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Do not approve the release (please provide specific comments)
>>
>> This vote will be open for 72 hours.
>>
>> Thanks,
>> Regards
>> JB
>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1 (binding)
Regards
JB
On 01/19/2015 02:53 PM, Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit Apache Karaf Cellar 3.0.1 release to your vote.
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12327148
>
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1019/
>
> Git tag:
> cellar-3.0.1
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Do not approve the release (please provide specific comments)
>
> This vote will be open for 72 hours.
>
> Thanks,
> Regards
> JB
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Regarding the log, IMHO, it doesn't come directly from Cellar but more
from the Hazelcast 3.3.4 update.
BUT, I just tried and I don't reproduce your issue (even with child
instances), and it's an use case that I tested a lot.
Do you install the cellar feature exactly in the same time on the two
instances ? Can you try to first install Cellar on node1, wait that the
installation is complete, and install after on node2 ?
Thanks,
Regards
JB
On 01/21/2015 06:55 AM, Achim Nierbeck wrote:
> Hi,
>
> no I didn't change the hazelcast XML.
> Cause this worked in previous versions automatically, I would regard a
> regression.
>
> Regards, Achim
>
> sent from mobile device
> Am 21.01.2015 06:43 schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:
>
>> Did you change the etc/hazelcast.xml ?
>>
>> It works fine for me (with "standalone" instances at least). I try with
>> child instance.
>>
>> Regards
>> JB
>>
>> On 01/21/2015 12:15 AM, Achim Nierbeck wrote:
>>
>>> -1
>>>
>>> following test scenario failed for me twice.
>>> Using the latest Karaf 3.0.3-SNAPSHOT version
>>>
>>> steps to reproduce:
>>>
>>> 1/ creating a second instance with instance:create second
>>> 2/ starting the second instance with instance:start second
>>> 3/ adding the cellar feature to both instances
>>> 4/ installing the 3.0.1 cellar feature in both instances
>>>
>>> karaf@root()> cluster:node-list
>>> | Id | Host Name | Port
>>> -------------------------------------
>>> x | 10.34.0.1:5701 | 10.34.0.1 | 5701
>>>
>>> this is the second node started.
>>>
>>> karaf@playbook()> cluster:node-list
>>> | Id | Host Name | Port
>>> -------------------------------------
>>> x | 10.34.0.1:5702 | 10.34.0.1 | 5702
>>>
>>>
>>> following is displayed in the second log:
>>>
>>> 2015-01-21 00:09:19,387 | INFO | FelixStartLevel | LifecycleService
>>> | 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar]
>>> [3.3.4]
>>> Address[10.34.0.1]:5702 is STARTING
>>> 2015-01-21 00:09:22,242 | INFO | FelixStartLevel | MulticastJoiner
>>> | 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar]
>>> [3.3.4]
>>>
>>>
>>> Members [1] {
>>> Member [10.34.0.1]:5702 this
>>> }
>>>
>>> 2015-01-21 00:09:22,243 | WARN | FelixStartLevel | Node
>>> | 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar]
>>> [3.3.4]
>>> Config seed port is 5701 and cluster size is 1. Some of the ports seem
>>> occupied!
>>> 2015-01-21 00:09:22,262 | INFO | FelixStartLevel | LifecycleService
>>> | 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar]
>>> [3.3.4]
>>> Address[10.34.0.1]:5702 is STARTED
>>> 2015-01-21 00:09:22,297 | INFO | FelixStartLevel |
>>> InternalPartitionService | 66 - com.hazelcast - 3.3.4 |
>>> [10.34.0.1]:5702 [cellar] [3.3.4] Initializing cluster partition table
>>> first arrangement...
>>>
>>>
>>> Did play through this scenario two times.
>>>
>>> This message:
>>> Config seed port is 5701 and cluster size is 1. Some of the ports seem
>>> occupied!
>>>
>>> worries me.
>>>
>>> regards, Achim
>>>
>>>
>>>
>>> Am 20. Januar 2015 um 08:47 schrieb Andy Schmidt <Andy.Schmidt@kisters.de
>>>> :
>>>
>>> +1
>>>>
>>>>
>>>> ------------------------------------------------------------
>>>> ------------------------------------------------------------
>>>> --------------------
>>>> Andy Schmidt - KISTERS AG - Pascalstraße 8+10 - 52076 Aachen - Germany
>>>> Handelsregister Aachen, HRB-Nr. 7838 | Vorstand: Klaus Kisters, Hanns
>>>> Kisters | Aufsichtsratsvorsitzender: Dr. Thomas Klevers
>>>> Phone: +49 2408 9385 -449 | Fax: +49 2408 9385 -555 | E-Mail:
>>>> Andy.Schmidt@kisters.de | WWW: http://www.kisters.de
>>>>
>>>> ------------------------------------------------------------
>>>> ------------------------------------------------------------
>>>> --------------------
>>>> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
>>>> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
>>>> E-Mail
>>>> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
>>>> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
>>>> Weitergabe dieser Mail ist nicht gestattet.
>>>> This e-mail may contain confidential and/or privileged information. If
>>>> you
>>>> are not the intended recipient (or have received this e-mail in error)
>>>> please notify the sender immediately and destroy this e-mail. Any
>>>> unauthorised copying, disclosure or distribution of the material in this
>>>> e-mail is strictly forbidden.
>>>>
>>>> From: Jean-Baptiste Onofré <jb...@nanthrax.net>
>>>> To: "dev@karaf >> Karaf Dev" <de...@karaf.apache.org>,
>>>> Date: 19.01.2015 15:20
>>>> Subject: [VOTE] Apache Karaf Cellar 3.0.1 release
>>>>
>>>>
>>>>
>>>> Hi all,
>>>>
>>>> I submit Apache Karaf Cellar 3.0.1 release to your vote.
>>>>
>>>> Release Notes:
>>>>
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>>> projectId=12311140&version=12327148
>>>>
>>>>
>>>> Staging Repository:
>>>> https://repository.apache.org/content/repositories/orgapachekaraf-1019/
>>>>
>>>> Git tag:
>>>> cellar-3.0.1
>>>>
>>>> Please vote to approve this release:
>>>>
>>>> [ ] +1 Approve the release
>>>> [ ] -1 Do not approve the release (please provide specific comments)
>>>>
>>>> This vote will be open for 72 hours.
>>>>
>>>> Thanks,
>>>> Regards
>>>> JB
>>>> --
>>>> Jean-Baptiste Onofré
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi,
no I didn't change the hazelcast XML.
Cause this worked in previous versions automatically, I would regard a
regression.
Regards, Achim
sent from mobile device
Am 21.01.2015 06:43 schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:
> Did you change the etc/hazelcast.xml ?
>
> It works fine for me (with "standalone" instances at least). I try with
> child instance.
>
> Regards
> JB
>
> On 01/21/2015 12:15 AM, Achim Nierbeck wrote:
>
>> -1
>>
>> following test scenario failed for me twice.
>> Using the latest Karaf 3.0.3-SNAPSHOT version
>>
>> steps to reproduce:
>>
>> 1/ creating a second instance with instance:create second
>> 2/ starting the second instance with instance:start second
>> 3/ adding the cellar feature to both instances
>> 4/ installing the 3.0.1 cellar feature in both instances
>>
>> karaf@root()> cluster:node-list
>> | Id | Host Name | Port
>> -------------------------------------
>> x | 10.34.0.1:5701 | 10.34.0.1 | 5701
>>
>> this is the second node started.
>>
>> karaf@playbook()> cluster:node-list
>> | Id | Host Name | Port
>> -------------------------------------
>> x | 10.34.0.1:5702 | 10.34.0.1 | 5702
>>
>>
>> following is displayed in the second log:
>>
>> 2015-01-21 00:09:19,387 | INFO | FelixStartLevel | LifecycleService
>> | 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar]
>> [3.3.4]
>> Address[10.34.0.1]:5702 is STARTING
>> 2015-01-21 00:09:22,242 | INFO | FelixStartLevel | MulticastJoiner
>> | 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar]
>> [3.3.4]
>>
>>
>> Members [1] {
>> Member [10.34.0.1]:5702 this
>> }
>>
>> 2015-01-21 00:09:22,243 | WARN | FelixStartLevel | Node
>> | 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar]
>> [3.3.4]
>> Config seed port is 5701 and cluster size is 1. Some of the ports seem
>> occupied!
>> 2015-01-21 00:09:22,262 | INFO | FelixStartLevel | LifecycleService
>> | 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar]
>> [3.3.4]
>> Address[10.34.0.1]:5702 is STARTED
>> 2015-01-21 00:09:22,297 | INFO | FelixStartLevel |
>> InternalPartitionService | 66 - com.hazelcast - 3.3.4 |
>> [10.34.0.1]:5702 [cellar] [3.3.4] Initializing cluster partition table
>> first arrangement...
>>
>>
>> Did play through this scenario two times.
>>
>> This message:
>> Config seed port is 5701 and cluster size is 1. Some of the ports seem
>> occupied!
>>
>> worries me.
>>
>> regards, Achim
>>
>>
>>
>> Am 20. Januar 2015 um 08:47 schrieb Andy Schmidt <Andy.Schmidt@kisters.de
>> >:
>>
>> +1
>>>
>>>
>>> ------------------------------------------------------------
>>> ------------------------------------------------------------
>>> --------------------
>>> Andy Schmidt - KISTERS AG - Pascalstraße 8+10 - 52076 Aachen - Germany
>>> Handelsregister Aachen, HRB-Nr. 7838 | Vorstand: Klaus Kisters, Hanns
>>> Kisters | Aufsichtsratsvorsitzender: Dr. Thomas Klevers
>>> Phone: +49 2408 9385 -449 | Fax: +49 2408 9385 -555 | E-Mail:
>>> Andy.Schmidt@kisters.de | WWW: http://www.kisters.de
>>>
>>> ------------------------------------------------------------
>>> ------------------------------------------------------------
>>> --------------------
>>> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
>>> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
>>> E-Mail
>>> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
>>> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
>>> Weitergabe dieser Mail ist nicht gestattet.
>>> This e-mail may contain confidential and/or privileged information. If
>>> you
>>> are not the intended recipient (or have received this e-mail in error)
>>> please notify the sender immediately and destroy this e-mail. Any
>>> unauthorised copying, disclosure or distribution of the material in this
>>> e-mail is strictly forbidden.
>>>
>>> From: Jean-Baptiste Onofré <jb...@nanthrax.net>
>>> To: "dev@karaf >> Karaf Dev" <de...@karaf.apache.org>,
>>> Date: 19.01.2015 15:20
>>> Subject: [VOTE] Apache Karaf Cellar 3.0.1 release
>>>
>>>
>>>
>>> Hi all,
>>>
>>> I submit Apache Karaf Cellar 3.0.1 release to your vote.
>>>
>>> Release Notes:
>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>> projectId=12311140&version=12327148
>>>
>>>
>>> Staging Repository:
>>> https://repository.apache.org/content/repositories/orgapachekaraf-1019/
>>>
>>> Git tag:
>>> cellar-3.0.1
>>>
>>> Please vote to approve this release:
>>>
>>> [ ] +1 Approve the release
>>> [ ] -1 Do not approve the release (please provide specific comments)
>>>
>>> This vote will be open for 72 hours.
>>>
>>> Thanks,
>>> Regards
>>> JB
>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>>>
>>>
>>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Did you change the etc/hazelcast.xml ?
It works fine for me (with "standalone" instances at least). I try with
child instance.
Regards
JB
On 01/21/2015 12:15 AM, Achim Nierbeck wrote:
> -1
>
> following test scenario failed for me twice.
> Using the latest Karaf 3.0.3-SNAPSHOT version
>
> steps to reproduce:
>
> 1/ creating a second instance with instance:create second
> 2/ starting the second instance with instance:start second
> 3/ adding the cellar feature to both instances
> 4/ installing the 3.0.1 cellar feature in both instances
>
> karaf@root()> cluster:node-list
> | Id | Host Name | Port
> -------------------------------------
> x | 10.34.0.1:5701 | 10.34.0.1 | 5701
>
> this is the second node started.
>
> karaf@playbook()> cluster:node-list
> | Id | Host Name | Port
> -------------------------------------
> x | 10.34.0.1:5702 | 10.34.0.1 | 5702
>
>
> following is displayed in the second log:
>
> 2015-01-21 00:09:19,387 | INFO | FelixStartLevel | LifecycleService
> | 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar] [3.3.4]
> Address[10.34.0.1]:5702 is STARTING
> 2015-01-21 00:09:22,242 | INFO | FelixStartLevel | MulticastJoiner
> | 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar] [3.3.4]
>
>
> Members [1] {
> Member [10.34.0.1]:5702 this
> }
>
> 2015-01-21 00:09:22,243 | WARN | FelixStartLevel | Node
> | 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar] [3.3.4]
> Config seed port is 5701 and cluster size is 1. Some of the ports seem
> occupied!
> 2015-01-21 00:09:22,262 | INFO | FelixStartLevel | LifecycleService
> | 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar] [3.3.4]
> Address[10.34.0.1]:5702 is STARTED
> 2015-01-21 00:09:22,297 | INFO | FelixStartLevel |
> InternalPartitionService | 66 - com.hazelcast - 3.3.4 |
> [10.34.0.1]:5702 [cellar] [3.3.4] Initializing cluster partition table
> first arrangement...
>
>
> Did play through this scenario two times.
>
> This message:
> Config seed port is 5701 and cluster size is 1. Some of the ports seem
> occupied!
>
> worries me.
>
> regards, Achim
>
>
>
> Am 20. Januar 2015 um 08:47 schrieb Andy Schmidt <An...@kisters.de>:
>
>> +1
>>
>>
>> --------------------------------------------------------------------------------------------------------------------------------------------
>> Andy Schmidt - KISTERS AG - Pascalstraße 8+10 - 52076 Aachen - Germany
>> Handelsregister Aachen, HRB-Nr. 7838 | Vorstand: Klaus Kisters, Hanns
>> Kisters | Aufsichtsratsvorsitzender: Dr. Thomas Klevers
>> Phone: +49 2408 9385 -449 | Fax: +49 2408 9385 -555 | E-Mail:
>> Andy.Schmidt@kisters.de | WWW: http://www.kisters.de
>>
>> --------------------------------------------------------------------------------------------------------------------------------------------
>> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
>> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
>> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
>> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
>> Weitergabe dieser Mail ist nicht gestattet.
>> This e-mail may contain confidential and/or privileged information. If you
>> are not the intended recipient (or have received this e-mail in error)
>> please notify the sender immediately and destroy this e-mail. Any
>> unauthorised copying, disclosure or distribution of the material in this
>> e-mail is strictly forbidden.
>>
>> From: Jean-Baptiste Onofré <jb...@nanthrax.net>
>> To: "dev@karaf >> Karaf Dev" <de...@karaf.apache.org>,
>> Date: 19.01.2015 15:20
>> Subject: [VOTE] Apache Karaf Cellar 3.0.1 release
>>
>>
>>
>> Hi all,
>>
>> I submit Apache Karaf Cellar 3.0.1 release to your vote.
>>
>> Release Notes:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12327148
>>
>>
>> Staging Repository:
>> https://repository.apache.org/content/repositories/orgapachekaraf-1019/
>>
>> Git tag:
>> cellar-3.0.1
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Do not approve the release (please provide specific comments)
>>
>> This vote will be open for 72 hours.
>>
>> Thanks,
>> Regards
>> JB
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>>
>>
>>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
By the way, another solution would be to downgrade the Hazelcast version
(allowing both), but in that case we loose a bunch of enhancements and
performance improvements (and bug fixes ;)).
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é" <jb...@nanthrax.net>:
>
>> It seems that I reproduce the same behavior by disable promisc/multicast
>> on my network interface. Just disabling multicast and enabling tcp-ip in
>> etc/hazelcast.xml fixes the problem.
>>
>> Regards
>> JB
>>
>> On 01/21/2015 07:21 AM, Jean-Baptiste Onofré 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 and
>>> disable tcp-ip.
>>>
>>> If your interface or network doesn't support multicast, it will fail to
>>> discover the nodes.
>>>
>>> Can you try to change to tcp-ip (with localhost) instead of multicast ?
>>>
>>> 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é
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Thanks for the update Achim.
I'm discussing with Hazelcast guys to understand why they changed this
and their plan.
Regards
JB
On 01/21/2015 08:26 PM, Achim Nierbeck wrote:
> Ok, I'll revert my -1 to a not so happy +1 (binding)
> after changing the hazelcast file it also works on mac
>
> regards, Achim
>
> 2015-01-21 10:28 GMT+01:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
>
>> Good point, I will add a note in the documentation.
>>
>> Regards
>> JB
>>
>>
>> On 01/21/2015 09:42 AM, Achim Nierbeck wrote:
>>
>>> Hi,
>>>
>>> I'll only be able to test this later this evening. Never the less this
>>> will
>>> be an issue for a couple people then.
>>> We need to have a hint for that at least.
>>>
>>> Regards, Achim
>>>
>>> sent from mobile device
>>> Am 21.01.2015 09:11 schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:
>>>
>>> Yes, but previously we use both: multicast AND tcp-ip. So even if it
>>>> didn't work in multicast, it uses tcp-ip. So maybe your interface never
>>>> 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
>>>>> need
>>>>> to file a bug at hazelcast then?
>>>>>
>>>>> Regards, Achim
>>>>>
>>>>> sent from mobile device
>>>>> Am 21.01.2015 09:02 schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:
>>>>>
>>>>> 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
>>>>>> regression
>>>>>> for user using multicast on different machines. It will work in your
>>>>>> case
>>>>>> for node on a single machine without multicast support on the interface
>>>>>> (by
>>>>>> the way, it's the config used in hazelcast module tests as the tests
>>>>>> run
>>>>>> on
>>>>>> a single machine)
>>>>>> 2/ enabling multicast and disable tcp-ip: it's the current case, it
>>>>>> works
>>>>>> 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é" <jb...@nanthrax.net>:
>>>>>>>
>>>>>>> It seems that I reproduce the same behavior by disable
>>>>>>> promisc/multicast
>>>>>>>
>>>>>>> on my network interface. Just disabling multicast and enabling tcp-ip
>>>>>>>> in
>>>>>>>> etc/hazelcast.xml fixes the problem.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> JB
>>>>>>>>
>>>>>>>> On 01/21/2015 07:21 AM, Jean-Baptiste Onofré 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 and
>>>>>>>>> disable tcp-ip.
>>>>>>>>>
>>>>>>>>> If your interface or network doesn't support multicast, it will fail
>>>>>>>>> to
>>>>>>>>> discover the nodes.
>>>>>>>>>
>>>>>>>>> Can you try to change to tcp-ip (with localhost) instead of
>>>>>>>>> multicast
>>>>>>>>> ?
>>>>>>>>>
>>>>>>>>> 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é
>>>>>>>> jbonofre@apache.org
>>>>>>>> http://blog.nanthrax.net
>>>>>>>> Talend - http://www.talend.com
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>
>>>>>> Jean-Baptiste Onofré
>>>>>> jbonofre@apache.org
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>> Jean-Baptiste Onofré
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Achim Nierbeck <bc...@googlemail.com>.
Ok, I'll revert my -1 to a not so happy +1 (binding)
after changing the hazelcast file it also works on mac
regards, Achim
2015-01-21 10:28 GMT+01:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> Good point, I will add a note in the documentation.
>
> Regards
> JB
>
>
> On 01/21/2015 09:42 AM, Achim Nierbeck wrote:
>
>> Hi,
>>
>> I'll only be able to test this later this evening. Never the less this
>> will
>> be an issue for a couple people then.
>> We need to have a hint for that at least.
>>
>> Regards, Achim
>>
>> sent from mobile device
>> Am 21.01.2015 09:11 schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:
>>
>> Yes, but previously we use both: multicast AND tcp-ip. So even if it
>>> didn't work in multicast, it uses tcp-ip. So maybe your interface never
>>> 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
>>>> need
>>>> to file a bug at hazelcast then?
>>>>
>>>> Regards, Achim
>>>>
>>>> sent from mobile device
>>>> Am 21.01.2015 09:02 schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:
>>>>
>>>> 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
>>>>> regression
>>>>> for user using multicast on different machines. It will work in your
>>>>> case
>>>>> for node on a single machine without multicast support on the interface
>>>>> (by
>>>>> the way, it's the config used in hazelcast module tests as the tests
>>>>> run
>>>>> on
>>>>> a single machine)
>>>>> 2/ enabling multicast and disable tcp-ip: it's the current case, it
>>>>> works
>>>>> 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é" <jb...@nanthrax.net>:
>>>>>>
>>>>>> It seems that I reproduce the same behavior by disable
>>>>>> promisc/multicast
>>>>>>
>>>>>> on my network interface. Just disabling multicast and enabling tcp-ip
>>>>>>> in
>>>>>>> etc/hazelcast.xml fixes the problem.
>>>>>>>
>>>>>>> Regards
>>>>>>> JB
>>>>>>>
>>>>>>> On 01/21/2015 07:21 AM, Jean-Baptiste Onofré 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 and
>>>>>>>> disable tcp-ip.
>>>>>>>>
>>>>>>>> If your interface or network doesn't support multicast, it will fail
>>>>>>>> to
>>>>>>>> discover the nodes.
>>>>>>>>
>>>>>>>> Can you try to change to tcp-ip (with localhost) instead of
>>>>>>>> multicast
>>>>>>>> ?
>>>>>>>>
>>>>>>>> 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é
>>>>>>> jbonofre@apache.org
>>>>>>> http://blog.nanthrax.net
>>>>>>> Talend - http://www.talend.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>
>>>>> Jean-Baptiste Onofré
>>>>> jbonofre@apache.org
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>>
>>>>>
>>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Good point, I will add a note in the documentation.
Regards
JB
On 01/21/2015 09:42 AM, Achim Nierbeck wrote:
> Hi,
>
> I'll only be able to test this later this evening. Never the less this will
> be an issue for a couple people then.
> We need to have a hint for that at least.
>
> Regards, Achim
>
> sent from mobile device
> Am 21.01.2015 09:11 schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:
>
>> Yes, but previously we use both: multicast AND tcp-ip. So even if it
>> didn't work in multicast, it uses tcp-ip. So maybe your interface never
>> 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 need
>>> to file a bug at hazelcast then?
>>>
>>> Regards, Achim
>>>
>>> sent from mobile device
>>> Am 21.01.2015 09:02 schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:
>>>
>>> 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 regression
>>>> for user using multicast on different machines. It will work in your case
>>>> for node on a single machine without multicast support on the interface
>>>> (by
>>>> the way, it's the config used in hazelcast module tests as the tests run
>>>> on
>>>> a single machine)
>>>> 2/ enabling multicast and disable tcp-ip: it's the current case, it works
>>>> 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é" <jb...@nanthrax.net>:
>>>>>
>>>>> It seems that I reproduce the same behavior by disable
>>>>> promisc/multicast
>>>>>
>>>>>> on my network interface. Just disabling multicast and enabling tcp-ip
>>>>>> in
>>>>>> etc/hazelcast.xml fixes the problem.
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>> On 01/21/2015 07:21 AM, Jean-Baptiste Onofré 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 and
>>>>>>> disable tcp-ip.
>>>>>>>
>>>>>>> If your interface or network doesn't support multicast, it will fail
>>>>>>> to
>>>>>>> discover the nodes.
>>>>>>>
>>>>>>> Can you try to change to tcp-ip (with localhost) instead of multicast
>>>>>>> ?
>>>>>>>
>>>>>>> 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é
>>>>>> jbonofre@apache.org
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>> Jean-Baptiste Onofré
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi,
I'll only be able to test this later this evening. Never the less this will
be an issue for a couple people then.
We need to have a hint for that at least.
Regards, Achim
sent from mobile device
Am 21.01.2015 09:11 schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:
> Yes, but previously we use both: multicast AND tcp-ip. So even if it
> didn't work in multicast, it uses tcp-ip. So maybe your interface never
> 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 need
>> to file a bug at hazelcast then?
>>
>> Regards, Achim
>>
>> sent from mobile device
>> Am 21.01.2015 09:02 schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:
>>
>> 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 regression
>>> for user using multicast on different machines. It will work in your case
>>> for node on a single machine without multicast support on the interface
>>> (by
>>> the way, it's the config used in hazelcast module tests as the tests run
>>> on
>>> a single machine)
>>> 2/ enabling multicast and disable tcp-ip: it's the current case, it works
>>> 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é" <jb...@nanthrax.net>:
>>>>
>>>> It seems that I reproduce the same behavior by disable
>>>> promisc/multicast
>>>>
>>>>> on my network interface. Just disabling multicast and enabling tcp-ip
>>>>> in
>>>>> etc/hazelcast.xml fixes the problem.
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>> On 01/21/2015 07:21 AM, Jean-Baptiste Onofré 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 and
>>>>>> disable tcp-ip.
>>>>>>
>>>>>> If your interface or network doesn't support multicast, it will fail
>>>>>> to
>>>>>> discover the nodes.
>>>>>>
>>>>>> Can you try to change to tcp-ip (with localhost) instead of multicast
>>>>>> ?
>>>>>>
>>>>>> 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é
>>>>> jbonofre@apache.org
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>>
>>>>>
>>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Yes, but previously we use both: multicast AND tcp-ip. So even if it
didn't work in multicast, it uses tcp-ip. So maybe your interface never
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 need
> to file a bug at hazelcast then?
>
> Regards, Achim
>
> sent from mobile device
> Am 21.01.2015 09:02 schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:
>
>> 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 regression
>> for user using multicast on different machines. It will work in your case
>> for node on a single machine without multicast support on the interface (by
>> the way, it's the config used in hazelcast module tests as the tests run on
>> a single machine)
>> 2/ enabling multicast and disable tcp-ip: it's the current case, it works
>> 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é" <jb...@nanthrax.net>:
>>>
>>> It seems that I reproduce the same behavior by disable promisc/multicast
>>>> on my network interface. Just disabling multicast and enabling tcp-ip in
>>>> etc/hazelcast.xml fixes the problem.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 01/21/2015 07:21 AM, Jean-Baptiste Onofré 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 and
>>>>> disable tcp-ip.
>>>>>
>>>>> If your interface or network doesn't support multicast, it will fail to
>>>>> discover the nodes.
>>>>>
>>>>> Can you try to change to tcp-ip (with localhost) instead of multicast ?
>>>>>
>>>>> 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é
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Achim Nierbeck <bc...@googlemail.com>.
Strange, I didn't change anything on my Mac network interface. So we need
to file a bug at hazelcast then?
Regards, Achim
sent from mobile device
Am 21.01.2015 09:02 schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:
> 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 regression
> for user using multicast on different machines. It will work in your case
> for node on a single machine without multicast support on the interface (by
> the way, it's the config used in hazelcast module tests as the tests run on
> a single machine)
> 2/ enabling multicast and disable tcp-ip: it's the current case, it works
> 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é" <jb...@nanthrax.net>:
>>
>> It seems that I reproduce the same behavior by disable promisc/multicast
>>> on my network interface. Just disabling multicast and enabling tcp-ip in
>>> etc/hazelcast.xml fixes the problem.
>>>
>>> Regards
>>> JB
>>>
>>> On 01/21/2015 07:21 AM, Jean-Baptiste Onofré 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 and
>>>> disable tcp-ip.
>>>>
>>>> If your interface or network doesn't support multicast, it will fail to
>>>> discover the nodes.
>>>>
>>>> Can you try to change to tcp-ip (with localhost) instead of multicast ?
>>>>
>>>> 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é
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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
regression for user using multicast on different machines. It will work
in your case for node on a single machine without multicast support on
the interface (by the way, it's the config used in hazelcast module
tests as the tests run on a single machine)
2/ enabling multicast and disable tcp-ip: it's the current case, it
works 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é" <jb...@nanthrax.net>:
>
>> It seems that I reproduce the same behavior by disable promisc/multicast
>> on my network interface. Just disabling multicast and enabling tcp-ip in
>> etc/hazelcast.xml fixes the problem.
>>
>> Regards
>> JB
>>
>> On 01/21/2015 07:21 AM, Jean-Baptiste Onofré 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 and
>>> disable tcp-ip.
>>>
>>> If your interface or network doesn't support multicast, it will fail to
>>> discover the nodes.
>>>
>>> Can you try to change to tcp-ip (with localhost) instead of multicast ?
>>>
>>> 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é
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Achim Nierbeck <bc...@googlemail.com>.
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é" <jb...@nanthrax.net>:
> It seems that I reproduce the same behavior by disable promisc/multicast
> on my network interface. Just disabling multicast and enabling tcp-ip in
> etc/hazelcast.xml fixes the problem.
>
> Regards
> JB
>
> On 01/21/2015 07:21 AM, Jean-Baptiste Onofré 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 and
>> disable tcp-ip.
>>
>> If your interface or network doesn't support multicast, it will fail to
>> discover the nodes.
>>
>> Can you try to change to tcp-ip (with localhost) instead of multicast ?
>>
>> 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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
It seems that I reproduce the same behavior by disable promisc/multicast
on my network interface. Just disabling multicast and enabling tcp-ip in
etc/hazelcast.xml fixes the problem.
Regards
JB
On 01/21/2015 07:21 AM, Jean-Baptiste Onofré 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 and
> disable tcp-ip.
>
> If your interface or network doesn't support multicast, it will fail to
> discover the nodes.
>
> Can you try to change to tcp-ip (with localhost) instead of multicast ?
>
> 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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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 and
disable tcp-ip.
If your interface or network doesn't support multicast, it will fail to
discover the nodes.
Can you try to change to tcp-ip (with localhost) instead of multicast ?
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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Achim Nierbeck <bc...@googlemail.com>.
-1
following test scenario failed for me twice.
Using the latest Karaf 3.0.3-SNAPSHOT version
steps to reproduce:
1/ creating a second instance with instance:create second
2/ starting the second instance with instance:start second
3/ adding the cellar feature to both instances
4/ installing the 3.0.1 cellar feature in both instances
karaf@root()> cluster:node-list
| Id | Host Name | Port
-------------------------------------
x | 10.34.0.1:5701 | 10.34.0.1 | 5701
this is the second node started.
karaf@playbook()> cluster:node-list
| Id | Host Name | Port
-------------------------------------
x | 10.34.0.1:5702 | 10.34.0.1 | 5702
following is displayed in the second log:
2015-01-21 00:09:19,387 | INFO | FelixStartLevel | LifecycleService
| 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar] [3.3.4]
Address[10.34.0.1]:5702 is STARTING
2015-01-21 00:09:22,242 | INFO | FelixStartLevel | MulticastJoiner
| 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar] [3.3.4]
Members [1] {
Member [10.34.0.1]:5702 this
}
2015-01-21 00:09:22,243 | WARN | FelixStartLevel | Node
| 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar] [3.3.4]
Config seed port is 5701 and cluster size is 1. Some of the ports seem
occupied!
2015-01-21 00:09:22,262 | INFO | FelixStartLevel | LifecycleService
| 66 - com.hazelcast - 3.3.4 | [10.34.0.1]:5702 [cellar] [3.3.4]
Address[10.34.0.1]:5702 is STARTED
2015-01-21 00:09:22,297 | INFO | FelixStartLevel |
InternalPartitionService | 66 - com.hazelcast - 3.3.4 |
[10.34.0.1]:5702 [cellar] [3.3.4] Initializing cluster partition table
first arrangement...
Did play through this scenario two times.
This message:
Config seed port is 5701 and cluster size is 1. Some of the ports seem
occupied!
worries me.
regards, Achim
Am 20. Januar 2015 um 08:47 schrieb Andy Schmidt <An...@kisters.de>:
> +1
>
>
> --------------------------------------------------------------------------------------------------------------------------------------------
> Andy Schmidt - KISTERS AG - Pascalstraße 8+10 - 52076 Aachen - Germany
> Handelsregister Aachen, HRB-Nr. 7838 | Vorstand: Klaus Kisters, Hanns
> Kisters | Aufsichtsratsvorsitzender: Dr. Thomas Klevers
> Phone: +49 2408 9385 -449 | Fax: +49 2408 9385 -555 | E-Mail:
> Andy.Schmidt@kisters.de | WWW: http://www.kisters.de
>
> --------------------------------------------------------------------------------------------------------------------------------------------
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail ist nicht gestattet.
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorised copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
>
> From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> To: "dev@karaf >> Karaf Dev" <de...@karaf.apache.org>,
> Date: 19.01.2015 15:20
> Subject: [VOTE] Apache Karaf Cellar 3.0.1 release
>
>
>
> Hi all,
>
> I submit Apache Karaf Cellar 3.0.1 release to your vote.
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12327148
>
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1019/
>
> Git tag:
> cellar-3.0.1
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Do not approve the release (please provide specific comments)
>
> This vote will be open for 72 hours.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
>
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: [VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Andy Schmidt <An...@kisters.de>.
+1
--------------------------------------------------------------------------------------------------------------------------------------------
Andy Schmidt - KISTERS AG - Pascalstraße 8+10 - 52076 Aachen - Germany
Handelsregister Aachen, HRB-Nr. 7838 | Vorstand: Klaus Kisters, Hanns Kisters | Aufsichtsratsvorsitzender: Dr. Thomas Klevers
Phone: +49 2408 9385 -449 | Fax: +49 2408 9385 -555 | E-Mail: Andy.Schmidt@kisters.de | WWW: http://www.kisters.de
--------------------------------------------------------------------------------------------------------------------------------------------
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
From: Jean-Baptiste Onofré <jb...@nanthrax.net>
To: "dev@karaf >> Karaf Dev" <de...@karaf.apache.org>,
Date: 19.01.2015 15:20
Subject: [VOTE] Apache Karaf Cellar 3.0.1 release
Hi all,
I submit Apache Karaf Cellar 3.0.1 release to your vote.
Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12327148
Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1019/
Git tag:
cellar-3.0.1
Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Do not approve the release (please provide specific comments)
This vote will be open for 72 hours.
Thanks,
Regards
JB
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
[RESULT][VOTE] Apache Karaf Cellar 3.0.1 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi all,
this vote passed with the following result:
+1 (binding): Achim Nierbeck (reverted from -1), Jean-Baptiste Onofré,
Jamie Goodyear, Andreas Pieber
+1 (non binding): Andy Schmidt
I'm promiting the artifacts on central, update Jira and website, and
send the announcement e-mail.
Thanks all for your vote.
Regards
JB
On 01/19/2015 02:53 PM, Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit Apache Karaf Cellar 3.0.1 release to your vote.
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12327148
>
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1019/
>
> Git tag:
> cellar-3.0.1
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Do not approve the release (please provide specific comments)
>
> This vote will be open for 72 hours.
>
> Thanks,
> Regards
> JB
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com