How to configure a custom Hazelcast when using the component camel-hazelcast

Solution Verified - Updated -

Issue

Using camel-hazelcast it starts a local (in JVM/classloader) Hazelcast cluster, by loading a default hazelcast configuration file 'hazelcast-default.xml' from classpath:

2016-12-09 09:59:22,088 | INFO  | ExtenderThread-4 | XmlConfigLocator                 | 360 - com.hazelcast - 3.6.2 | Loading 'hazelcast-default.xml' from classpath.
2016-12-09 09:59:22,174 | INFO  | ExtenderThread-4 | DefaultAddressPicker             | 360 - com.hazelcast - 3.6.2 | [LOCAL] [dev] [3.6.2] Prefer IPv4 stack is true.
2016-12-09 09:59:22,175 | INFO  | AMQ-1-thread-1   | ActiveMQServiceFactory           | 231 - io.fabric8.mq.mq-fabric - 1.2.0.redhat-630187 | Broker root has started.
2016-12-09 09:59:22,179 | INFO  | ExtenderThread-4 | DefaultAddressPicker             | 360 - com.hazelcast - 3.6.2 | [LOCAL] [dev] [3.6.2] Picked Address[10.36.5.16]:5701, using socket ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=5701], bind any local is true
2016-12-09 09:59:22,190 | INFO  | ExtenderThread-4 | system                           | 360 - com.hazelcast - 3.6.2 | [10.36.5.16]:5701 [dev] [3.6.2] Hazelcast 3.6.2 (20160405 - 0f88699) starting at Address[10.36.5.16]:5701

Environment

  • Red Hat JBoss Fuse
    • 6.3.0
  • hazelcast
    • 3.6.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content