Hi You can likely handle that in your custom aggregator, so when an exception was thrown, then return an empty aggregated value, or mark the exchange as "failed" so when it restarts later then its either empty or you know it failed as you marked it.
On Tue, Jun 3, 2014 at 7:56 PM, karthik.subramanian2 <karthik.subramani...@target.com> wrote: > Hi, > > I have a custom aggregation strategy from which another camel route is > called using a producer template. > When an exception occurs in the sub route, the aggregator's old exchange > does not get cleared as the aggregation completion size is not complete as > per the route definition. > When i restart the whole process , the last failed exchange remains in the > oldExchange of the aggregator rather than becoming null. > > I know that there is an aggregation repository that stores all the > exchanges, but in this case i want the aggregator to know that there has > been an exception and when it gets invoked for the next time, it should > start from scratch rather than picking up the failed exchange. > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Aggregator-retains-the-old-exchange-in-case-of-exception-tp5751849.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
