It could be, or maybe there is only 1 file that is not changed. The read lock is only granted if Camel "sees" the file as not being changed (which is that its file size / timestamp) is not changing over a period of time.
On Wed, Apr 24, 2013 at 1:29 PM, hefiso <henrik.filtenborg.soren...@gmail.com> wrote: > Hi > > Usually the file-endpoint (File2) allows for processing more than one file > per poll by setting the property maxMessagesPerPoll. > > However, when also using readLock=changed, then the file-consumer does not > consume more than one file per poll, regardless of the value specified for > maxMessagesPerPoll. When changing readLock back to "markerFile" then the > file endpoint is again able to consume several files per poll. > > I am surprised by this behaviour, is it by design or should I log a JIRA? > > Best regards > Henrik > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/File2-maxMessagesPerPoll-combined-with-readLock-changed-tp5731434.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
