Camel Hazelcast Component creating multiple instances of Hazelcast

[Ayache Khettar <ay...@googlemail.com>]

Hi

I have started using Camel Hazelcast for distributed caching but realised
that all the bundles using the Camel hazelcast component create a new
instance of Hazelcast. So 11bundles will result in 11 members joined in in
one single JVM and the list is growing.

Is this a healthy thing - see below hazelcast log? Hazelcast documentation
doesn't explicitly says how many members you should have per JVM. I am
inclined to think it should be limited to small number or even to one
member per JVM.

Camel Hazelcast component does not have support for joining an already
running instance of Hazelcast, I think it should.


Any ideas how best to set up hazelcast/camel in one single JVM would be
very much appreciated.

Ayache


Members [11] {
Member [xxx.168.xxx.221]:5701
Member [xxx.168.xxx.221]:5702
Member [xxx.168.xxx.221]:5703
Member [xxx.168.xxx.221]:5705
Member [xxx.168.xxx.221]:5706
Member [xxx.168.xxx.221]:5707
Member [xxx.168.xxx.221]:5708 this
Member [xxx.168.xxx.221]:5709
Member [xxx.168.xxx.221]:5710
Member [xxx.168.xxx.221]:5704
Member [xxx.168.xxx.221]:5711
}

Re: Camel Hazelcast Component creating multiple instances of Hazelcast

["ayache.k" <ay...@gmail.com>]

Hi Willem

Thanks for your prompt response. The support for hazelcastInstance is on
camel 2.14 I didn't realise that. I will explore that further. You mentioned
I may need to expose the instance as a service, can you show me an example?
the documentation doesn't sow that.

Thanks



--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Hazelcast-Component-creating-multiple-instances-of-Hazelcast-tp5764283p5764320.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Hazelcast Component creating multiple instances of Hazelcast

[Willem Jiang <wi...@gmail.com>]

Hi,

Camel Hazelcast endpoint supports to set the Hazelcast instance with the option of hazelcastInstance=#INSTANCE_NAME.

You may need to write a hazelcastInstance service for it if you want to share some hazelcastInstance across the JVM.

--  
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem



On March 17, 2015 at 11:27:07 PM, Ayache Khettar (ayache.khettar@googlemail.com) wrote:
> Hi
>  
> I have started using Camel Hazelcast for distributed caching but realised
> that all the bundles using the Camel hazelcast component create a new
> instance of Hazelcast. So 11bundles will result in 11 members joined in in
> one single JVM and the list is growing.
>  
> Is this a healthy thing - see below hazelcast log? Hazelcast documentation
> doesn't explicitly says how many members you should have per JVM. I am
> inclined to think it should be limited to small number or even to one
> member per JVM.
>  
> Camel Hazelcast component does not have support for joining an already
> running instance of Hazelcast, I think it should.
>  
>  
> Any ideas how best to set up hazelcast/camel in one single JVM would be
> very much appreciated.
>  
> Ayache
>  
>  
> Members [11] {
> Member [xxx.168.xxx.221]:5701
> Member [xxx.168.xxx.221]:5702
> Member [xxx.168.xxx.221]:5703
> Member [xxx.168.xxx.221]:5705
> Member [xxx.168.xxx.221]:5706
> Member [xxx.168.xxx.221]:5707
> Member [xxx.168.xxx.221]:5708 this
> Member [xxx.168.xxx.221]:5709
> Member [xxx.168.xxx.221]:5710
> Member [xxx.168.xxx.221]:5704
> Member [xxx.168.xxx.221]:5711
> }
>