There is a JIRA ticket to improved the resequencer to allow a pluggable repository. AFAIK its the last stateful EIP that doesnt offer that. Another stateful EIP is the idempotent consumer.
On Thu, May 19, 2011 at 9:44 AM, janne postilista <[email protected]> wrote: > Some of the EIP patterns are stateful. For example aggregator collects > a group of messages 1-2-3 and sends the aggregated one once all 3 have > arrived. When messages 1 and 2 have arrived, state = messages 1 and 2. > Another example is resequencer. > > We are running multiple (now 2) instances of Camel to provide > failover. Clustering is based on JMS queues. Messages arrive in input > queue, a route (either camel instance A or B) reads the message and > does some processing, writes the message to intermediate queue 1, some > other route (from A or B) reads that message, etc, until the message > is written to output queue. > > Is there some general Camel solution for working with stateful EIP > patterns in clustered environment? State could be persisted in shared > database. It seems aggregator http://camel.apache.org/aggregator2.html > supports this, jdbc-aggregationrepository is mentioned. However > others, such as resequencer http://camel.apache.org/resequencer.html, > do not have the same feature. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com CamelOne 2011: http://fusesource.com/camelone2011/ Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
