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 process. On Wed, May 17, 2017 at 1:39 PM, codentravel <shivaprashan...@gmail.com> wrote: > Thanks for the reply. > I did exactly the same yesterday.. It seem to be working fine.. > > Do you have any suggestion bring the CPU down ? > Currently it consumes about 70% of CPU (beaglebone with 1gb of RAM) for 15 > messages/second. Is it normal for Camel to consume so much of CPU ? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Redelivery-of-message-in-case-of-exception-inside-aggregator-tp5799551p5799704.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
