You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/12/07 20:00:12 UTC
[jira] [Commented] (KARAF-3014) Hazelcast tests fail on networks
where multicast is disabled
[ https://issues.apache.org/jira/browse/KARAF-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045492#comment-15045492 ]
ASF GitHub Bot commented on KARAF-3014:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/karaf-cellar/pull/1
> Hazelcast tests fail on networks where multicast is disabled
> ------------------------------------------------------------
>
> Key: KARAF-3014
> URL: https://issues.apache.org/jira/browse/KARAF-3014
> Project: Karaf
> Issue Type: Bug
> Components: cellar-hazelcast
> Affects Versions: cellar-2.3.2
> Reporter: Hadrian Zbarcea
> Assignee: Jean-Baptiste Onofré
> Fix For: cellar-3.0.0, cellar-2.3.3
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)