Hi, I am using camel 2.12 version currently. There is an issue related to 'camelfilelength not getting updated in header properly, for long write file during SFTP' in this version. I could see that this issue has been fixed in camel 2.18.0 as part of CAMEL-9970.
I tried with 2.18.2 version with NO readlock parameters and the issue is still occurring. 2.18.2 version with different readLockTimeout and readLockCheckInterval also leads to issue (ex-readLock=changed&readLockTimeout=40000&readLockCheckInterval=10000) 2.18.2 version with readLockMinAge alone is solving the issue. (ex-readLock=changed&readLockMinAge=300s) Now my question is, if the upgraded camel version too would not solve the issue without readLockMinAge parameter, then, is there any way we can solve the issue with 2.12 version itself just by additional SFTP camel attributes. Because, I wanted to upgrade camel jars just to solve this camelfilelength issue during SFTP and I will end up testing all the camel flows in my application. Also, I could see 'CamelLogger - Cannot acquire read lock within 20000 millis. Will skip the file: RemoteFile[filename]' is occurring even after the file is transferred completely. Why should we get this error with default period (20sec) when I have not configured readLockTimeout and just readLockMinAge is configured to 120 seconds. This error is misleading, but I'm still able to hide this error by providing readLockLoggingLevel=OFF Regards, Siva -- View this message in context: http://camel.465427.n5.nabble.com/CamelFilelength-Issue-in-Message-Header-during-SFTP-tp5793930.html Sent from the Camel - Users mailing list archive at Nabble.com.
