Change hazelcast.xml default to tcp-ip + localhost
Hazelcast communication using multi-cast with default address may
interfere with other host who happens to be on the same network.
e.g.,When the code is checked-out and user immediately run mvn test, etc.
This is a short term workaround to address the issue by
changing the default to tcp-ip and forming cluster using localhost only.
Change-Id: I762edd6b37ccdb689c8b6493b60fdca7a8f1a0e1
diff --git a/conf/hazelcast.xml b/conf/hazelcast.xml
index cf44fc3..68575c6 100644
--- a/conf/hazelcast.xml
+++ b/conf/hazelcast.xml
@@ -91,19 +91,19 @@
<network>
<port auto-increment="true">5701</port>
<join>
- <multicast enabled="true">
- <multicast-group>224.2.2.3</multicast-group>
- <multicast-port>54327</multicast-port>
+ <multicast enabled="false">
+ <multicast-group>224.2.2.3</multicast-group>
+ <multicast-port>54327</multicast-port>
</multicast>
- <!--
- <tcp-ip enabled="false">
- <member>machine1</member>
- <member>machine2</member>
- <member>machine3:5799</member>
- <member>192.168.1.0-7</member>
- <member>192.168.1.21</member>
- </tcp-ip>
+ <tcp-ip enabled="true">
+ <member>localhost</member>
+ <!--
+ <member>machine2</member>
+ <member>machine3:5799</member>
+ <member>192.168.1.0-7</member>
+ <member>192.168.1.21</member>
-->
+ </tcp-ip>
<aws enabled="false">
</aws>
</join>