Re: Redelivery of message in case of exception inside aggregator

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

Redelivery of message in case of exception inside aggregator

Hi, In my aggregationstratgy route, sometimes (1 out of 1) 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 ? rest

Re: Sometimes the data in body is null..

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

Sometimes the data in body is null..

I have the following route strategy- JAVA DSL restConfiguration().component("restlet") .componentProperty("maxQueued", "-1") .componentProperty("persistingConnections", "true") .componentProperty("pipeliningConnections", "true")