[
https://issues.apache.org/jira/browse/CAMEL-11434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16513022#comment-16513022
]
Jason Carreira commented on CAMEL-11434:
----------------------------------------
I just had to add this block back to my camel configuration:
@Bean(name = "hazelcast")
HazelcastComponent hazelcastComponent() {
HazelcastComponent hazelcastComponent = new HazelcastComponent();
hazelcastComponent.setHazelcastInstance(hazelcastInstance);
return hazelcastComponent;
}
because I noticed that multiple hazelcast instances were being created and
connecting to each other during my integration tests. I set breakpoints and
they were being created by the DefaultHazelcastComponent.
getOrCreateHzInstance() method. The implementing class was still the deprecated
HazelcastComponent.
> camel-hazelcast: auto discovery of hazelcast instances in spring-boot
> ---------------------------------------------------------------------
>
> Key: CAMEL-11434
> URL: https://issues.apache.org/jira/browse/CAMEL-11434
> Project: Camel
> Issue Type: Improvement
> Components: camel-hazelcast, camel-spring-boot-starters
> Reporter: Luca Burgazzoli
> Assignee: Luca Burgazzoli
> Priority: Minor
> Fix For: 2.20.0
>
>
> See:
> https://stackoverflow.com/questions/44660920/hazelcast-in-spring-boot-ignoring-my-networkconfig
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
