Thanks, Claus. This is great. To mitigate the possible issues from dangling threads, would you recommend that I use my own executorServiceRef that handles the timeouts gracefully?
On Tue, Jun 28, 2016 at 9:22 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > It depends if sending to those destinations fails with an exception, > then the aggregate method receives an exchange with the caused > exception. > > If you use timeout, then the aggregate method is not invoked, but you > can implement the TimeoutAwareAggregationStrategy to have a special > callback from those that times out. > > Mind that when using timeout that thread/process that is sending to > that destination is still running in the background - its not > magically killed - so use this with a bit care. > > > > On Tue, Jun 28, 2016 at 12:38 PM, Steve973 <steve...@gmail.com> wrote: > > Hello. In my application, I have a list of recipients, but at any time > > when I send messages to this list of recipients, it is possible that they > > may be unreachable. I want to aggregate responses, but how will the > > aggregation count be affected by unreachable destinations in the list? > > > > Thanks, > > Steve > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
