> In my aggregationstratgy route, sometimes (1 out of 10000) i get message
> body as null in the newExchange.. I have no clue whats wrong.
> Thought of trying the retry with default error handler. But Aggregator
> doesn't support throwing an exception. Is there any alternative to
> aggregator ?
> .componentProperty("maxQueued", "-1")
> .componentProperty("persistingConnections", "true")
> .componentProperty("pipeliningConnections", "true")
> route().routeId("Collector Inlet").
> routeId("Message Aggregation").
> setHeader("id", constant("n/a")).
> aggregate(header("id"), new MessageAggregation()).
> View this message in context: http://camel.465427.n5.nabble.com/Redelivery-of-message-in-case-of-exception-inside-aggregator-tp5799551.html > Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Redelivery of message in case of exception inside aggregator
I suggest to use a profiler to see what is going on in your JVM.
You may need to tweak restlet accordingly to your needs. You can set
limits on thread pools and whatnot.
And maybe also the load on the JVM if you have a lot of messages queued up etc.
Camel has little overhead, so its often other things you need to tweak.
However as you use SEDA with an unbounded queue you can end up with
too many messages pending, if you take in more messages than you can