On Mon, Oct 22, 2012 at 6:57 PM, swwyatt <steven.wy...@sungard.com> wrote: > We normally use readLock=rename for both file and sftp components. In a > deployment, we forgot to add the readLock option to an sftp route in a > cluster environment; both servers pulled the file. I was thinking that there > was a default, but maybe that is just for the file component. > > So is readLock=changed the only valid option for sftp? Seems that > readLock=rename works, but just not sure in a cluster. >
Ah yeah both are valid. rename and changed. The rename is generic and supported by any of the ftp/file components. Where as some have to be specific such as changed etc. > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/SFTP-readLock-option-tp5721403p5721406.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
