You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Zsolt Beothy-Elo (Created) (JIRA)" <ji...@apache.org> on 2012/03/28 16:09:27 UTC
[jira] [Created] (KARAF-1297) Switching off multicast discovery in
Cellar does not work properly
Switching off multicast discovery in Cellar does not work properly
------------------------------------------------------------------
Key: KARAF-1297
URL: https://issues.apache.org/jira/browse/KARAF-1297
Project: Karaf
Issue Type: Bug
Components: cellar-core
Affects Versions: cellar-2.2.4
Reporter: Zsolt Beothy-Elo
Setting the propery multicastEnabled to false has not the expected effect. Still the different Cellar are able to see each other.
Environmnet is two Karaf 2.2.5 containers on different hosts. The Cellar version used is 2.2.4 SNAPSHOT
Steps to reproduce the issue:
1) Start karaf on first host (node1).
2) install cellar feature
3) shutdown node1.
4) update configuration for node:
<org.apache.karaf.cellar.instance.cfg>:
multicastEnabled=false
multicastGroup=224.2.2.3
multicastPort=54327
multicastTimeoutSeconds=2
tcpIpEnabled=false
tcpIpMembers= MERGABLE[]
5) start karaf on second host (node2)
6) install cellar on node2
7) shutdown node2
8) update configuration of cellar on node2:
<org.apache.karaf.cellar.instance.cfg>:
multicastEnabled=false
multicastGroup=224.2.2.4
multicastPort=54328
multicastTimeoutSeconds=2
tcpIpEnabled=false
tcpIpMembers= MERGABLE[]
9) start node1
10) start node2
11) wait until all bundles are normally started
12) execute cluster:node-list on both nodes.
Expected to get only one node in output with host name on which it was executed, but output on both instances return two nodes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1297) Switching off multicast discovery
in Cellar does not work properly
Posted by "amasse (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242200#comment-13242200 ]
amasse commented on KARAF-1297:
-------------------------------
Hi,
I'm trying to connect two hosts (centos / serviceMix 4.4.0 / Cellar 2.2.3 ) but the multicast is disabled.
In fact with this issue, I could not connect the two hosts ? (and I have the problem)
Anthony
> Switching off multicast discovery in Cellar does not work properly
> ------------------------------------------------------------------
>
> Key: KARAF-1297
> URL: https://issues.apache.org/jira/browse/KARAF-1297
> Project: Karaf
> Issue Type: Bug
> Components: cellar-core
> Affects Versions: cellar-2.2.3
> Reporter: Zsolt Beothy-Elo
> Assignee: Jean-Baptiste Onofré
> Fix For: cellar-3.0.0, cellar-2.2.4
>
>
> Setting the propery multicastEnabled to false has not the expected effect. Still the different Cellar are able to see each other.
> Environmnet is two Karaf 2.2.5 containers on different hosts. The Cellar version used is 2.2.4 SNAPSHOT
> Steps to reproduce the issue:
> 1) Start karaf on first host (node1).
> 2) install cellar feature
> 3) shutdown node1.
> 4) update configuration for node:
> <org.apache.karaf.cellar.instance.cfg>:
> multicastEnabled=false
> multicastGroup=224.2.2.3
> multicastPort=54327
> multicastTimeoutSeconds=2
> tcpIpEnabled=false
> tcpIpMembers= MERGABLE[]
> 5) start karaf on second host (node2)
> 6) install cellar on node2
> 7) shutdown node2
> 8) update configuration of cellar on node2:
> <org.apache.karaf.cellar.instance.cfg>:
> multicastEnabled=false
> multicastGroup=224.2.2.4
> multicastPort=54328
> multicastTimeoutSeconds=2
> tcpIpEnabled=false
> tcpIpMembers= MERGABLE[]
> 9) start node1
> 10) start node2
> 11) wait until all bundles are normally started
> 12) execute cluster:node-list on both nodes.
> Expected to get only one node in output with host name on which it was executed, but output on both instances return two nodes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (KARAF-1297) Switching off multicast discovery in
Cellar does not work properly
Posted by "Jean-Baptiste Onofré (Assigned JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-1297:
-------------------------------------------
Assignee: Jean-Baptiste Onofré
> Switching off multicast discovery in Cellar does not work properly
> ------------------------------------------------------------------
>
> Key: KARAF-1297
> URL: https://issues.apache.org/jira/browse/KARAF-1297
> Project: Karaf
> Issue Type: Bug
> Components: cellar-core
> Affects Versions: cellar-2.2.4
> Reporter: Zsolt Beothy-Elo
> Assignee: Jean-Baptiste Onofré
>
> Setting the propery multicastEnabled to false has not the expected effect. Still the different Cellar are able to see each other.
> Environmnet is two Karaf 2.2.5 containers on different hosts. The Cellar version used is 2.2.4 SNAPSHOT
> Steps to reproduce the issue:
> 1) Start karaf on first host (node1).
> 2) install cellar feature
> 3) shutdown node1.
> 4) update configuration for node:
> <org.apache.karaf.cellar.instance.cfg>:
> multicastEnabled=false
> multicastGroup=224.2.2.3
> multicastPort=54327
> multicastTimeoutSeconds=2
> tcpIpEnabled=false
> tcpIpMembers= MERGABLE[]
> 5) start karaf on second host (node2)
> 6) install cellar on node2
> 7) shutdown node2
> 8) update configuration of cellar on node2:
> <org.apache.karaf.cellar.instance.cfg>:
> multicastEnabled=false
> multicastGroup=224.2.2.4
> multicastPort=54328
> multicastTimeoutSeconds=2
> tcpIpEnabled=false
> tcpIpMembers= MERGABLE[]
> 9) start node1
> 10) start node2
> 11) wait until all bundles are normally started
> 12) execute cluster:node-list on both nodes.
> Expected to get only one node in output with host name on which it was executed, but output on both instances return two nodes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (KARAF-1297) Switching off multicast discovery in
Cellar does not work properly
Posted by "Jean-Baptiste Onofré (Resolved JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-1297.
-----------------------------------------
Resolution: Fixed
> Switching off multicast discovery in Cellar does not work properly
> ------------------------------------------------------------------
>
> Key: KARAF-1297
> URL: https://issues.apache.org/jira/browse/KARAF-1297
> Project: Karaf
> Issue Type: Bug
> Components: cellar-core
> Affects Versions: cellar-2.2.3
> Reporter: Zsolt Beothy-Elo
> Assignee: Jean-Baptiste Onofré
> Fix For: cellar-3.0.0, cellar-2.2.4
>
>
> Setting the propery multicastEnabled to false has not the expected effect. Still the different Cellar are able to see each other.
> Environmnet is two Karaf 2.2.5 containers on different hosts. The Cellar version used is 2.2.4 SNAPSHOT
> Steps to reproduce the issue:
> 1) Start karaf on first host (node1).
> 2) install cellar feature
> 3) shutdown node1.
> 4) update configuration for node:
> <org.apache.karaf.cellar.instance.cfg>:
> multicastEnabled=false
> multicastGroup=224.2.2.3
> multicastPort=54327
> multicastTimeoutSeconds=2
> tcpIpEnabled=false
> tcpIpMembers= MERGABLE[]
> 5) start karaf on second host (node2)
> 6) install cellar on node2
> 7) shutdown node2
> 8) update configuration of cellar on node2:
> <org.apache.karaf.cellar.instance.cfg>:
> multicastEnabled=false
> multicastGroup=224.2.2.4
> multicastPort=54328
> multicastTimeoutSeconds=2
> tcpIpEnabled=false
> tcpIpMembers= MERGABLE[]
> 9) start node1
> 10) start node2
> 11) wait until all bundles are normally started
> 12) execute cluster:node-list on both nodes.
> Expected to get only one node in output with host name on which it was executed, but output on both instances return two nodes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-1297) Switching off multicast discovery in
Cellar does not work properly
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-1297:
----------------------------------------
Affects Version/s: (was: cellar-2.2.4)
cellar-2.2.3
Fix Version/s: cellar-2.2.4
cellar-3.0.0
> Switching off multicast discovery in Cellar does not work properly
> ------------------------------------------------------------------
>
> Key: KARAF-1297
> URL: https://issues.apache.org/jira/browse/KARAF-1297
> Project: Karaf
> Issue Type: Bug
> Components: cellar-core
> Affects Versions: cellar-2.2.3
> Reporter: Zsolt Beothy-Elo
> Assignee: Jean-Baptiste Onofré
> Fix For: cellar-3.0.0, cellar-2.2.4
>
>
> Setting the propery multicastEnabled to false has not the expected effect. Still the different Cellar are able to see each other.
> Environmnet is two Karaf 2.2.5 containers on different hosts. The Cellar version used is 2.2.4 SNAPSHOT
> Steps to reproduce the issue:
> 1) Start karaf on first host (node1).
> 2) install cellar feature
> 3) shutdown node1.
> 4) update configuration for node:
> <org.apache.karaf.cellar.instance.cfg>:
> multicastEnabled=false
> multicastGroup=224.2.2.3
> multicastPort=54327
> multicastTimeoutSeconds=2
> tcpIpEnabled=false
> tcpIpMembers= MERGABLE[]
> 5) start karaf on second host (node2)
> 6) install cellar on node2
> 7) shutdown node2
> 8) update configuration of cellar on node2:
> <org.apache.karaf.cellar.instance.cfg>:
> multicastEnabled=false
> multicastGroup=224.2.2.4
> multicastPort=54328
> multicastTimeoutSeconds=2
> tcpIpEnabled=false
> tcpIpMembers= MERGABLE[]
> 9) start node1
> 10) start node2
> 11) wait until all bundles are normally started
> 12) execute cluster:node-list on both nodes.
> Expected to get only one node in output with host name on which it was executed, but output on both instances return two nodes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-1297) Switching off multicast discovery
in Cellar does not work properly
Posted by "Jean-Baptiste Onofré (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252353#comment-13252353 ]
Jean-Baptiste Onofré commented on KARAF-1297:
---------------------------------------------
In KARAF-1248, I removed the etc/org.apache.karaf.cellar.instance.cfg file. Now, the only way to configure Cellar network is using the etc/hazelcast.xml.
I made a try:
* on node1, in etc/hazelcast.xml:
[...]
<network>
<port auto-increment="true">5701</port>
<join>
<multicast enabled="false">
<multicast-group>224.2.2.3</multicast-group>
<multicast-port>54327</multicast-port>
</multicast>
<tcp-ip enabled="true">
<interface>127.0.0.1:5701</interface>
</tcp-ip>
[...]
* on node2, in etc/hazelcast.xml:
[...]
<network>
<port auto-increment="true">5702</port>
<join>
<multicast enabled="false">
<multicast-group>224.2.2.3</multicast-group>
<multicast-port>54327</multicast-port>
</multicast>
<tcp-ip enabled="true">
<interface>127.0.0.1:5702</interface>
</tcp-ip>
[...]
I started each node:
karaf@node1> cluster:node-list
No. Host Name Port ID
* 1 localhost 5701 localhost:5701
karaf@node1>
and
karaf@node2> cluster:node-list
No. Host Name Port ID
* 1 localhost 5702 localhost:5702
karaf@node2>
> Switching off multicast discovery in Cellar does not work properly
> ------------------------------------------------------------------
>
> Key: KARAF-1297
> URL: https://issues.apache.org/jira/browse/KARAF-1297
> Project: Karaf
> Issue Type: Bug
> Components: cellar-core
> Affects Versions: cellar-2.2.3
> Reporter: Zsolt Beothy-Elo
> Assignee: Jean-Baptiste Onofré
> Fix For: cellar-3.0.0, cellar-2.2.4
>
>
> Setting the propery multicastEnabled to false has not the expected effect. Still the different Cellar are able to see each other.
> Environmnet is two Karaf 2.2.5 containers on different hosts. The Cellar version used is 2.2.4 SNAPSHOT
> Steps to reproduce the issue:
> 1) Start karaf on first host (node1).
> 2) install cellar feature
> 3) shutdown node1.
> 4) update configuration for node:
> <org.apache.karaf.cellar.instance.cfg>:
> multicastEnabled=false
> multicastGroup=224.2.2.3
> multicastPort=54327
> multicastTimeoutSeconds=2
> tcpIpEnabled=false
> tcpIpMembers= MERGABLE[]
> 5) start karaf on second host (node2)
> 6) install cellar on node2
> 7) shutdown node2
> 8) update configuration of cellar on node2:
> <org.apache.karaf.cellar.instance.cfg>:
> multicastEnabled=false
> multicastGroup=224.2.2.4
> multicastPort=54328
> multicastTimeoutSeconds=2
> tcpIpEnabled=false
> tcpIpMembers= MERGABLE[]
> 9) start node1
> 10) start node2
> 11) wait until all bundles are normally started
> 12) execute cluster:node-list on both nodes.
> Expected to get only one node in output with host name on which it was executed, but output on both instances return two nodes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira