Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
cellar-2.2.3
-
None
Description
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.
Attachments
Issue Links
- is related to
-
KARAF-1248 Avoid to duplicate configuration between hazelcast.xml and cellar instance cfg
- Resolved