[
https://issues.apache.org/jira/browse/CAMEL-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179934#comment-14179934
]
Nathan Jensen commented on CAMEL-6399:
--------------------------------------
Locks are tied to threads (the thread that locks must do the unlock) so if that
is an issue you could apply the same concept with Semaphores. See
http://stackoverflow.com/questions/19767328/in-hazelcast-is-it-possible-to-use-clustered-locks-that-do-not-care-about-the
and
http://docs.hazelcast.org/docs/3.3/javadoc/com/hazelcast/core/ISemaphore.html
> hazelcast - route policy for having one route being master, and others as
> slaves
> --------------------------------------------------------------------------------
>
> Key: CAMEL-6399
> URL: https://issues.apache.org/jira/browse/CAMEL-6399
> Project: Camel
> Issue Type: New Feature
> Components: camel-hazelcast
> Reporter: Claus Ibsen
> Fix For: Future
>
>
> We should look into adding a route policy functionality to camel-hazelcast.
> So people can use it clustered Camel apps. And have only one node run the
> route. And if that node dies, then another becomes master.
> Hazelcast may have som way of support this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
