On Fri, Feb 18, 2011 at 1:14 AM, rosmons <[email protected]> wrote: > > Hi Claus, > I've been trying to figure out if the TransactionErrorHandler actually > persists the message in between retries. > I can see from your post here that it's probably not implemented yet. I have > used the hawtdb as repo for Aggregation, but was wondering if you could > point me in the right way to do the same for the TransactionErrorHandler. > I wouldn't mind writing the additional code and could probably upload a > patch that can be used for future release if you find it useful. > The reason we need this is for the following scenario: > We have a topic which has durable consumers. > - The durable consumers receive a message > - Encounters an error while transmitting to a route > - in the OnException definition we have a RedeliveryPolicy which could run > upto 24hrs > - Let's say the camel context shutsdown due to some reason we loose the > message that is being redelivered >
Hi Usually the message broker have options for redelivery. By leveraging those instead, you ensure the message is kept persisted in the broker. I suggest you take a look at what the broker offers, instead of using Camel's redelivery. > if i can add persistence to the errorhandler it would solve this issue for > me. > > thanks > Rosmon > > -- > View this message in context: > http://camel.465427.n5.nabble.com/DefaultShutdownStrategy-can-t-shutdown-DefaultErrorHandler-s-retries-tp3276249p3390369.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
