I'm currently using camel-core-2.11.1.jar. In one of the routes, I'm using multicast, parallel processing with a time aware aggregation strategy. The goal is to perform a set of tasks simultaneously with a timeout upon aggregation.
In my load and performance testing, I noticed that a Java unbounded thread pool was created as the aggregateExecutor in MulticastProcessor, which has caused some of the performance issues in my application. Is there a way for me to pass or inject a bounded Java thread pool for the aggregation effort as it does not have to be that big in my case? If not, are there any other alternatives for the fork-n-join processing in Camel? Thanks, Connie -- View this message in context: http://camel.465427.n5.nabble.com/How-to-pass-a-bounded-Java-threadpool-as-the-aggregateExecutorService-in-MulticastProcessor-tp5738170.html Sent from the Camel - Users mailing list archive at Nabble.com.
