Hi Claus, The problem can happen with multicast, even if there is no aggregation strategy.
If in the last branch exchange of multicast, stream caching happens (and also clean up of file on completion of branch), then if the next step (processor) after multicast tries to read the data from the incoming exchange, same issue will happen. Pls. try to handle this aspect as well as part of the same JIRA. Thanks, Lakshmi -- View this message in context: http://camel.465427.n5.nabble.com/Stream-Cache-spool-file-deletion-before-aggregation-in-Multicast-involving-huge-data-tp5756092p5756160.html Sent from the Camel - Users mailing list archive at Nabble.com.
