I propose to extend the value eagerMaxMessagesPerPoll in file/ftp consumers.
eagerMaxMessagesPerPoll = true eagerMaxMessagesPerPoll = false eagerMaxMessagesPerPoll = reach eagerMaxMessagesPerPoll = overcome The values of "reach" and "overcome" give a chance to correct sorting of files in a single directory. Get a list of files in a directory. files = operations.listFiles(); For values of "true" and "false", a model of behavior remains the same. eagerMaxMessagesPerPoll = reach First filter the files. If the number of files in a directory exceeds the limit (maxMessagesPerPoll) and to read the list is empty, stop at the limit. If the total number of the previously selected files in the current directory and the value exceeds maxMessagesPerPoll, exit the method doPollDirectory with the result false. If you have not reached the limit (maxMessagesPerPoll), add files to the general list. Treat subdirectories. eagerMaxMessagesPerPoll = overcome First filter the files. Adding files to the general list. If the limit is reached or exceeded (maxMessagesPerPoll), exit the method doPollDirectory with the result false. If you have not reached the limit (maxMessagesPerPoll), treat subdirectories. --- Aleksey -- View this message in context: http://camel.465427.n5.nabble.com/Propose-change-eagerMaxMessagesPerPoll-in-file-ftp-consumers-tp5766299.html Sent from the Camel - Users mailing list archive at Nabble.com.
