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
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 m
It can be because the message body from REST is streaming based
http://camel.apache.org/why-is-my-message-body-empty.html
And also you send to seda and don't wait, hence the REST consumer may
close the stream before the aggregator is aggregating the newExchange.
So you should likely convert the m
