Thanks for the suggestion. yeah currently i am trying to log all the details .. I suspect network connection .
I need to handle 10 messages(~600 byte) /s received on the rest endpoint, aggregate these in batches 100 then, add some metadata and publish on a message bus. This will have to run 24/7 . This module will run as a plugin and will be loaded/initialized in the main application. This should work on a basic hardware with Linux(something like a beaglebone/pi). Currently the CPU usage (<40% during peak time) and memory looks fine so i am ok with default threadpool .. There was some lag earlier but disabling the streamcaching helped. But i am not too sure what changes can be made on that. -- View this message in context: http://camel.465427.n5.nabble.com/Sometimes-the-data-in-body-is-null-tp5798624p5798630.html Sent from the Camel - Users mailing list archive at Nabble.com.
