On Tue, Dec 4, 2012 at 3:55 PM, swwyatt wrote:
> When the SFTP component writes a file, does it use the
> 'camelExclusiveReadLock' extension or is this just for consumer?
>
Just for consumers. They are read locks, and all apply for consumers only.
>
>
> --
&g
When the SFTP component writes a file, does it use the
'camelExclusiveReadLock' extension or is this just for consumer?
--
View this message in context:
http://camel.465427.n5.nabble.com/camelExclusiveReadLock-tp5723619.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Claus
Both SFTP and camel are running on windows 2003.
Doing a check on the file timestamp did cross our minds.
So I believe we would be implementing a new strategy.
But I think we will probably try and convince our client to change their
upload process
as this works great for our other clie
Hi
Is the FTP server running on Windows 2003, or is it where Camel runs?
A good strategy is of course to write using a temporary name, and then
at the end do a move/rename.
Then the consumer should "just avoid" trying to poll the "temporary files".
Camel with the rename strategy is using the ren
Camel 2.7, Windows 2003
Continuing on from this issue
http://camel.465427.n5.nabble.com/SFTP-rename-problems-td478681.html#a478683
We recently moved to version 2.7.
And are polling files from a sftp server.
We have two client that are writing files to folder which we are scanning.
One uploads
