You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by hopey_dishwasher <na...@gmail.com> on 2015/09/01 13:06:15 UTC
"TcpIpJoinerOverAWS not found by com.hazelcast" when discovering
cellar nodes on AWS
I'm trying to get Cellar working on some AWS instances.
*TL;DR version: *
Karaf 3.0.4 + Cellar 3.0.3 + AWS hazelcast autodiscovery doesn't seem to
work. The hazelcast bundle it installs is missing the class
com.hazelcast.cluster.impl.TcpIpJoinerOverAWS.
*Longer version:*
I've got a fresh install of Karaf 3.0.4. I've configured hazelcast.xml based
on the example here
<http://karaf.apache.org/manual/cellar/latest-3/user-guide/hazelcast.html>
. I've run:
karaf@root()> feature:repo-add
mvn:org.apache.karaf.cellar/apache-karaf-cellar/3.0.3/xml/features
karaf@root()> feature:install cellar
And I get the following in the logs:
org.osgi.service.blueprint.container.ComponentDefinitionException:
org.osgi.service.blueprint.container.ComponentDefinitionException: Error
when instantiating bean hazelcast of class com.hazelcast.core.Hazelcast
at
org.apache.aries.blueprint.container.ServiceRecipe.createService(ServiceRecipe.java:309)[15:org.apache.aries.blueprint.core:1.4.3]
... many lines of stack trace ...
Caused by: java.lang.ClassNotFoundException:
com.hazelcast.cluster.impl.TcpIpJoinerOverAWS not found by com.hazelcast
[66]
at
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1532)
On closer inspection (of data/cache), it's installed hazelcast 3.4.2 as a
feature as a transitive dependency of cellar, and the hazelcast jar it
installs does not include com.hazelcast.cluster.impl.TcpIpJoinerOverAWS.
However, if I download hazelcast 3.4.2 manually elsewhere, it does include
that class.
(I've also tried a couple of other combinations of Karaf 3.0.x and Cellar
3.0.y, with the same results)
Is there something I'm doing wrong here, or does AWS discovery just not work
out of the box?
Alternatively, can I get it to use a different source for the hazelcast
distribution, so that I can use one that includes the class in question.
Cheers
--
View this message in context: http://karaf.922171.n3.nabble.com/TcpIpJoinerOverAWS-not-found-by-com-hazelcast-when-discovering-cellar-nodes-on-AWS-tp4042232.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: "TcpIpJoinerOverAWS not found by com.hazelcast" when discovering
cellar nodes on AWS
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I think the discovery service documentation is not so bad:
http://karaf.apache.org/manual/cellar/latest-3/user-guide/cloud.html
Regards
JB
On 09/01/2015 02:04 PM, Achim Nierbeck wrote:
> Hi,
>
> the last time I used the cellar-cloud feature it worked.
> It's been a while (2013), but if I remember correctly you just need to
> make sure you
> have the "cloud provider" and the storage configured.
> So for example if you use a S3, you need to add that blob-storage.
> See also here [1].
>
> regards, Achim
> [1] - http://karaf.apache.org/manual/cellar/latest-3/user-guide/cloud.html
>
>
> 2015-09-01 13:33 GMT+02:00 Jean-Baptiste Onofré <jb@nanthrax.net
> <ma...@nanthrax.net>>:
>
> Cellar 3.0.4 and 4.0.0.
>
> Regards
> JB
>
>
> On 09/01/2015 01:28 PM, hopey_dishwasher wrote:
>
> No, cellar-cloud isn't installed. I'd be happy to use that if it
> works, but I
> haven't been able to find any documentation thorough enough to
> actually get
> anything working.
>
> What release are you referring to? Like cellar 3.0.4, or karaf
> 3.0.5, or
> 4.x?
>
> Cheers
>
>
> jbonofre wrote
>
> Hi
>
> you don't use Cellar discovery (cellar-cloud) service, right ?
>
> For Hazelcast, I think it's related to the update to
> hazelcast-all
> (already done, coming in the next release).
>
> Regards
> JB
>
>
>
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/TcpIpJoinerOverAWS-not-found-by-com-hazelcast-when-discovering-cellar-nodes-on-AWS-tp4042232p4042236.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
>
>
> --
>
> Apache Member
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
> & Project Lead
> blog <http://notizblog.nierbeck.de/>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>
> Software Architect / Project Manager / Scrum Master
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: "TcpIpJoinerOverAWS not found by com.hazelcast" when discovering
cellar nodes on AWS
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi,
the last time I used the cellar-cloud feature it worked.
It's been a while (2013), but if I remember correctly you just need to make
sure you
have the "cloud provider" and the storage configured.
So for example if you use a S3, you need to add that blob-storage.
See also here [1].
regards, Achim
[1] - http://karaf.apache.org/manual/cellar/latest-3/user-guide/cloud.html
2015-09-01 13:33 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> Cellar 3.0.4 and 4.0.0.
>
> Regards
> JB
>
>
> On 09/01/2015 01:28 PM, hopey_dishwasher wrote:
>
>> No, cellar-cloud isn't installed. I'd be happy to use that if it works,
>> but I
>> haven't been able to find any documentation thorough enough to actually
>> get
>> anything working.
>>
>> What release are you referring to? Like cellar 3.0.4, or karaf 3.0.5, or
>> 4.x?
>>
>> Cheers
>>
>>
>> jbonofre wrote
>>
>>> Hi
>>>
>>> you don't use Cellar discovery (cellar-cloud) service, right ?
>>>
>>> For Hazelcast, I think it's related to the update to hazelcast-all
>>> (already done, coming in the next release).
>>>
>>> Regards
>>> JB
>>>
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://karaf.922171.n3.nabble.com/TcpIpJoinerOverAWS-not-found-by-com-hazelcast-when-discovering-cellar-nodes-on-AWS-tp4042232p4042236.html
>> Sent from the Karaf - User mailing list archive at Nabble.com.
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: "TcpIpJoinerOverAWS not found by com.hazelcast" when discovering
cellar nodes on AWS
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Cellar 3.0.4 and 4.0.0.
Regards
JB
On 09/01/2015 01:28 PM, hopey_dishwasher wrote:
> No, cellar-cloud isn't installed. I'd be happy to use that if it works, but I
> haven't been able to find any documentation thorough enough to actually get
> anything working.
>
> What release are you referring to? Like cellar 3.0.4, or karaf 3.0.5, or
> 4.x?
>
> Cheers
>
>
> jbonofre wrote
>> Hi
>>
>> you don't use Cellar discovery (cellar-cloud) service, right ?
>>
>> For Hazelcast, I think it's related to the update to hazelcast-all
>> (already done, coming in the next release).
>>
>> Regards
>> JB
>
>
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/TcpIpJoinerOverAWS-not-found-by-com-hazelcast-when-discovering-cellar-nodes-on-AWS-tp4042232p4042236.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: "TcpIpJoinerOverAWS not found by com.hazelcast" when
discovering cellar nodes on AWS
Posted by hopey_dishwasher <na...@gmail.com>.
No, cellar-cloud isn't installed. I'd be happy to use that if it works, but I
haven't been able to find any documentation thorough enough to actually get
anything working.
What release are you referring to? Like cellar 3.0.4, or karaf 3.0.5, or
4.x?
Cheers
jbonofre wrote
> Hi
>
> you don't use Cellar discovery (cellar-cloud) service, right ?
>
> For Hazelcast, I think it's related to the update to hazelcast-all
> (already done, coming in the next release).
>
> Regards
> JB
--
View this message in context: http://karaf.922171.n3.nabble.com/TcpIpJoinerOverAWS-not-found-by-com-hazelcast-when-discovering-cellar-nodes-on-AWS-tp4042232p4042236.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: "TcpIpJoinerOverAWS not found by com.hazelcast" when discovering
cellar nodes on AWS
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
you don't use Cellar discovery (cellar-cloud) service, right ?
For Hazelcast, I think it's related to the update to hazelcast-all
(already done, coming in the next release).
Regards
JB
On 09/01/2015 01:06 PM, hopey_dishwasher wrote:
> I'm trying to get Cellar working on some AWS instances.
>
> *TL;DR version: *
>
> Karaf 3.0.4 + Cellar 3.0.3 + AWS hazelcast autodiscovery doesn't seem to
> work. The hazelcast bundle it installs is missing the class
> com.hazelcast.cluster.impl.TcpIpJoinerOverAWS.
>
> *Longer version:*
>
> I've got a fresh install of Karaf 3.0.4. I've configured hazelcast.xml based
> on the example here
> <http://karaf.apache.org/manual/cellar/latest-3/user-guide/hazelcast.html>
> . I've run:
>
> karaf@root()> feature:repo-add
> mvn:org.apache.karaf.cellar/apache-karaf-cellar/3.0.3/xml/features
> karaf@root()> feature:install cellar
>
> And I get the following in the logs:
>
> org.osgi.service.blueprint.container.ComponentDefinitionException:
> org.osgi.service.blueprint.container.ComponentDefinitionException: Error
> when instantiating bean hazelcast of class com.hazelcast.core.Hazelcast
> at
> org.apache.aries.blueprint.container.ServiceRecipe.createService(ServiceRecipe.java:309)[15:org.apache.aries.blueprint.core:1.4.3]
> ... many lines of stack trace ...
> Caused by: java.lang.ClassNotFoundException:
> com.hazelcast.cluster.impl.TcpIpJoinerOverAWS not found by com.hazelcast
> [66]
> at
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1532)
>
>
> On closer inspection (of data/cache), it's installed hazelcast 3.4.2 as a
> feature as a transitive dependency of cellar, and the hazelcast jar it
> installs does not include com.hazelcast.cluster.impl.TcpIpJoinerOverAWS.
> However, if I download hazelcast 3.4.2 manually elsewhere, it does include
> that class.
>
> (I've also tried a couple of other combinations of Karaf 3.0.x and Cellar
> 3.0.y, with the same results)
>
>
> Is there something I'm doing wrong here, or does AWS discovery just not work
> out of the box?
>
> Alternatively, can I get it to use a different source for the hazelcast
> distribution, so that I can use one that includes the class in question.
>
> Cheers
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/TcpIpJoinerOverAWS-not-found-by-com-hazelcast-when-discovering-cellar-nodes-on-AWS-tp4042232.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com