Re: [HEADS UP] Camel K is here!

2018-10-16 Thread Andrea Cosentino
YAY! -- Andrea Cosentino  -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Wednesday, October 17, 2018, 12:24:37 AM GMT+2, Nicola Ferraro wrote: Hi folks, aft

[HEADS UP] Camel K is here!

2018-10-16 Thread Nicola Ferraro
Hi folks, after some months of brainstorming with the community and a bit more than one month of development, our Camel K project has reached a good level of stability and I've published the first blog post about it yesterday. For those of you who haven't heard of Camel K, it's now a subproject of

concurrentConsumers create duplicated messages and fail

2018-10-16 Thread Damien Nicolas
Hello, I have a Springboot war with Camel routes deployed on a JBoss EAP 7.1 server. The routes are generated dynamically and some of them have *concurrentConsumers > 1* because a route can have several times the same processor; example (here a schematically representation of a route): cxf -> jms

Re: throttling/backpressure on a route

2018-10-16 Thread Onder SEZGIN
Hi, I would suggest 1- Take a look at throttle-eip. (Make sure you understand split, aggregate and mongodb3 producer adocs around mongodb aggregation. Try and see your case unless you can explain or create a unit test to pinpoint your issue and also check mongodb3 components test case for better ex

throttling/backpressure on a route

2018-10-16 Thread Peter Nagy (Jr)
Newbie question incoming. I have a route that looks like ... .setHeader("CamelMongoDbBatchSize", 128) .to("mongodb3:mymongo?...&operation=aggregate&outputType=MongoIterable") .split(constant(true)) .streaming() ... .aggregate(constant(true), new GroupedBodyAggregationStrategy()) .completionSize(1