Thanks for the reply Claus. That explains the behavior I have been seeing Essentially, I was expecting wrongly of asyncprocessors to kick off a separate thread and continue processing the exchange.
Thanks, Brian -- View this message in context: http://camel.465427.n5.nabble.com/Processing-Asynchronous-Interceptors-tp5738810p5739067.html Sent from the Camel - Users mailing list archive at Nabble.com.
