Hello, This seems like most appropriate place to post a question like this involving many open source parts.
I am looking for the best solution on creating a manageable runtime environment which includes running business logic written with camel and deployed to Karaf (JBoss Buse 6.0). Some camel routes use camel-hazelcast component and out of the box each such route spawns its own hazelcast node. When those camel routes are deployed to different karaf containers running on the same physical machine, you essentially create a mesh of hazelcast nodes - some in same JVMs, some in others. This is simple, but does not "feel right", especially you have no High Availability, as if one server burns out, to many hazelcast nodes die. If camel-hazelcast component could be configured to act only as a "lite client" as once was called i believe (prior to version 3), or as hazelcast client. That would be step 1. And the step 2 would be to apply hazelcast profile (Fuse lingo) to a karaf container to become a hazelcast instance, like it is possible with ActiveMQ by applying mq profile. That way an even number of servers would run a container acting as hazelcast instance creating a scalable solution separating data cluster from application cluster. If anyone here can share some ideas, I would be grateful. Best regards, borut
