I upgraded my dev box to version 2.8.3 so I could use the readLockCheckInterval option and set it to 3 seconds. The Exchange still fires off even though the file hasn't completely copied. Details:
1) My custom Idempotent Repository gets queried as soon as I initiate the file copy (OK) 2) 3 seconds later the incoming Exchange is logged and processes even though the 1GB file is not completely copied. In the Windows Explorer 'details' view, the file size shows 1GB even though only maybe 200MB have been transferred. It seems like for my case increasing the readLockCheckInterval doesn't help b/c Windows reports the final file size even though it hasn't finished copying. From searching (and from documentation in the Camel File component), it's a common problem but I've never run into it before. I'm going to look at the code from the current changed read lock as you suggested to see if I can figure something out for our scenario. We will have write permissions for the file so maybe I can determine file completion that way. I'll post back on the status. This issue appears when I'm copying between local directories and from a network drive btw. -- View this message in context: http://camel.465427.n5.nabble.com/Inconsistent-results-with-File2-readLock-changed-tp5030004p5033493.html Sent from the Camel - Users mailing list archive at Nabble.com.
