Quartz suports running in a clustered environment where it can trigger tasks to only run on one node.
On Tue, Jan 25, 2011 at 6:33 PM, Alfred Hiebl <a.hi...@mic-cust.com> wrote: > > Hi, > > I'd like to ask for a best practice for a situation which I hope to be a > common use-case. In our routes we consume data from polling endpoints like > mail or file which do not support concurrent consumers out-of-the-box. We > need CRON schedules; so plan to use camel-quartz together with pollEnrich. > > We want to deploy Camel in a Tomcat server on two app server nodes. For > load-balancing and availability reasons the same routes should run on both > nodes. > > How do I best avoid duplicate processing of messages? Do I need to implement > a mutex-type function myself or is there an easier way to guarantee this in > Camel? > > Best regards, > Alfred > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Schedule-file-mail-endpoint-tp3356666p3356666.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
