Note, the FtpChangedRenameReadLockStrategy combines the 'changed' and the 'rename' read lock strategy. It first calls acquire on GenericFileRenameExclusiveReadLockStrategy, followed by a acquire call on FtpChangedExclusiveReadLockStrategy.
This is because the @#$%^&* SAP system first creates an empty file, and -while holding on to the file- fills it with data. -- View this message in context: http://camel.465427.n5.nabble.com/Content-Length-and-CamelFileLength-suddenly-0-tp5776967p5777141.html Sent from the Camel - Users mailing list archive at Nabble.com.
