camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CAMEL-4271) jdbc aggregation repository - recovery taks and cluster issue
Date Tue, 26 Jul 2011 14:37:09 GMT
jdbc aggregation repository - recovery taks and cluster issue
-------------------------------------------------------------

                 Key: CAMEL-4271
                 URL: https://issues.apache.org/jira/browse/CAMEL-4271
             Project: Camel
          Issue Type: Improvement
          Components: camel-core, camel-sql
    Affects Versions: 2.8.0
            Reporter: Claus Ibsen
             Fix For: Future


If you enable recovery on the aggregator eip when using a persistent repository such as the
jdbc, then you may have a race condition when having multiple camel apps running in a cluster.
As the aggregate recover task is running on each Camel app (node) in the cluster. So they
may potentially all pickup recovery tasks, and execute those, which may cause duplicate messages
being recovered.

What is needed is a lock table or some other way to ensure only one recover tasks "wins" and
executes.

We may want to enhance the API in camel to facilitate this kind of locking. As with hawtdb
you may have a shared file on the SAN and thus have the same racing issue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message