[
https://issues.apache.org/jira/browse/KARAF-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013030#comment-14013030
]
ASF GitHub Bot commented on KARAF-3014:
---------------------------------------
GitHub user hzbarcea opened a pull request:
https://github.com/apache/karaf-cellar/pull/1
KARAF-3014. Fix for using multicast in tests and other build fixes.
See https://issues.apache.org/jira/browse/KARAF-3014
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hzbarcea/karaf-cellar master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/karaf-cellar/pull/1.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1
----
commit 4d9381e85c58a1297c70f2e5ceef5edb1cd2273a
Author: Hadrian Zbarcea <hadr...@apache.org>
Date: 2014-05-29T19:48:59Z
Fix crlf for NOTICE files
commit 8a12075beffea05ec39f4819b4ee8bc4986bf759
Author: Hadrian Zbarcea <hadr...@apache.org>
Date: 2014-05-29T19:54:03Z
Fix karaf dependency version so that build doesn't fail
commit 1d0a4376876252e85f4dd408dce774da6b93675d
Author: Hadrian Zbarcea <hadr...@apache.org>
Date: 2014-05-29T22:29:39Z
KARAF-3014. Use tcp instead of multicast for tests
----
> 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
> Fix For: cellar-3.0.0
>
>
> 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.2#6252)
