What do you think of this approach?
MulticastProcessor should pass in it’s own AsyncCallback (or attach a
Synchronization if you perfer) where on done() we submit the Exchange to be
aggregated. That way if the route is async no threads are blocked waiting for a
response, essentially it would be
What do you think of this approach?
MulticastProcessor should pass in it’s own AsyncCallback (or attach a
Synchronization if you perfer) where on done() we submit the Exchange to be
aggregated. That way if the route is async no threads are blocked waiting for a
response, essentially it would be
Camel riders,
I'm seeing an issue caused by the MulticastProcessor not handling async
routing end-to-end. It does use its own threadpool to process its routing
tasks, as well as to perform the aggregation (on-the-fly).
However, during all that time, the calling thread is blocked waiting for
the m
