Does the route start processing the file, but not finish processing? I would expect you’d see some messages in the logs from the DefaultShutdownStrategy about inflight exchanges, but they should complete. Have you customized the shutdown strategy?
> On Mar 16, 2016, at 11:38 AM, jamesburn <[email protected]> wrote: > > Hi > > Interesting. > > I'd set maxMessagesPerPoll to ensure Camel doesn't try and process 100,000 > messages at once. I'd then realised this would probably limit the > CamelBatchSize, but by then couldn't get the CamelBatchComplete to trigger. > Anyway, I just took this out, and also the sendEmptyMessageWhenIdle=true out > (I put this in to try and stop the route when all the messages had been > collected; this was not needed.) > > And I set the Poolsize number. > > However, the CamelBatchComplete is still being set to true before all the > threads have completed - highlighted by a single file I artificially delay > not being moved (the route stops before it is moved). > > What drives CamelBatchComplete? > > Is there a different exchange flag I can access to let me know when the > process threads have completed? The parallel processing aspects are a bit of > a mystery to me. I've cobbled together BASH and Perl scripts to do this sort > of thing fine, but I'm floundering here. > > Thanks > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/file-trigger-processing-lots-of-files-tp5778807p5779172.html > Sent from the Camel - Users mailing list archive at Nabble.com.
