FileAsyncStressReadLockLockFileTest and maxMessagePerPoll
Can you explain a little bit more this comment in org.apache.camel.component.file.stress.FileAsyncStressReadLockLockFileTest?
// leverage the fact that we can limit to max 50 files per poll
// this will result in polling again and potentially picking up files
// that already are in progress
Is it safer to have a bigger or smaller maxMessagePerPoll in order to avoid picking files that are already in process? Is there a way to guaranty that a file will never be picked twice?
Re: FileAsyncStressReadLockLockFileTest and maxMessagePerPoll. picking twice
I ran various org.apache.camel.component.file.stress.FileAsyncStressTest tests and when the initial files in the inbox folder are 2000 and maxMessagesPerPoll is 50, I always get files being processed twice with all readLock options, except rename.Mind that I am using an additional move option to move processed files to an archive folder.