That is helpful. With the completionTimeout() I would like to group messages coming in through the webservice so that RouteB is not called multiple times. For example if there are 500 messages with the same payload coming in through the webservice, I would like to aggregate all of them into 1 message so that RouteB is called once.
With the seda implementation, I was attempting to make sure that only 1 instance of RouteB was running at one time. I think that changing seda:RouteB to direct:RouteB would accomplish what I need to do. I wasn't really clear on how the threading model worked. If it ensures sequential calls to RouteB, then it will accomplish what I need. Regards -- View this message in context: http://camel.465427.n5.nabble.com/SEDA-with-Aggregation-tp5789103p5789186.html Sent from the Camel - Users mailing list archive at Nabble.com.
