Notice from Camel 2.10 onwards the read locks changed, fileLock and rename will also use a markerFile as well, to ensure *not picking up files that may be in process by another Camel consumer *running on another node (eg cluster). This is only supported by the file component (*not the ftp component*).
-- View this message in context: http://camel.465427.n5.nabble.com/Camel-lock-while-multiple-routes-polling-from-same-file-endpoint-tp5751467p5751511.html Sent from the Camel - Users mailing list archive at Nabble.com.
