Buffering messages for batch processing

Hello all, I got into this similar design few times. I am not sure if I can use camel to cleanly code it. I get messages from a source at random times. For example document changed, record inserted .. etc. Invoking the processing for a single document is costly. For example indexing in lucene

Is there a Camel endpoint back-off algorithm?

I have a akka project which uses camel to communicate with the outside world. I observe a behavior that I don't know if it's true or how to control it. When sending some message to the endpoint URI, if the endpoint URI (e.g. http://somewhere.com) is not responding for any

Camel quartz - one scheduler used for a few QuartzComponent

Hi, My application consist of a few osgi modules and is running on Karaf environment. Each of those modules uses a camel-quartz component so for each module is created a quartz's scheduler. In effect a lot of threads is created becouse each scheduler consist of thread pool (default 10 threads)

Re: Upgrade to 2.16.0

Hi, I had the same ClassCaseException When To Filter after upgrading to 2.16.0. Seems like in 2.16 is only allowed inside . Outside you must use . Prior to 2.16 it was ok to use when outside -- View this message in context:

Re: Upgrade to 2.16.0

Can anyone show some route code with this problem. On Sat, Oct 24, 2015 at 11:55 AM, Clemens wrote: > Hi, > > I had the same ClassCaseException When To Filter after upgrading to 2.16.0. > Seems like in 2.16 is only allowed inside . Outside > you must use . Prior to 2.16 it