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?
--
View this message in context:
http://camel.465427.n5.nabble.com/FileAsyncStressReadLockLockFileTest-and-maxMessagePerPoll-tp5735083.html
Sent from the Camel - Users mailing list archive at Nabble.com.
