camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Suspending route/context if one component can't process messages
Date Thu, 07 Mar 2013 15:09:55 GMT

Yeah you can implement a custom PollingConsumerPollingStrategy

And then suspend/stop the consumer if it has failed to often.

On Wed, Mar 6, 2013 at 5:15 PM, DOLECEK Ales <> wrote:
> Hello,
>   I have endpoints that communicate with 3rd party proprietary backend server.
> If connection to the server is lost processing fails and Camel tries to
> re-process the exchanges again and again, until the connection is restored and
> the exchanges might pass through.
> Since there is high traffic on the route logs get full of exceptions and if the
> outage is long the ammount of undelivered exchanges increases (they come from
> filesystem and IMAP mailbox).
> What is the best stratégy to solve this? I'm considering to suspend context while
> The connection is down, but wonder if there is better way.
> Ales

Claus Ibsen
Red Hat, Inc.
FuseSource is now part of Red Hat
Twitter: davsclaus
Author of Camel in Action:

View raw message