[KARAF-3014] Hazelcast tests fail on networks where multicast is disabled

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: cellar-2.3.2
• Fix Version/s: cellar-3.0.0, cellar-2.3.3
• Component/s: cellar
• Assignee: Jean-Baptiste Onofré
• Reporter: Hadrian Zbarcea
• Created: 29/May/14 22:28
• Updated: 13/Sep/18 14:27
• Resolved: 12/Jun/14 19:36

Description

A new hazelcast instance will fail to join a cluster on networks where multicast is disabled. This can be solved via configuration on a production system, but the unit tests use the default configuration that from the hazelcast jar, which disables tcp and enables multicast. As a result one ends up with two clusters, on instance each instead of one cluster two instances.

Using a custom, minimal hazelcast.xml configuration solves the problem. See pull request.