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

Reply via email to