Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Ftp consumer
Date: Mon, 15 Sep 2008 11:28:39 +0200
Message-ID: <4C1FB9C00D24A140906239533638C4D20551C22B@EXVS04.exserver.dk>
In-Reply-To: <4C1FB9C00D24A140906239533638C4D20551C224@EXVS04.exserver.dk>
Thread-Topic: Ftp consumer
Thread-Index: AckXEzb9RR//DXvLRjOod9QfXMIVBAAAJ2GgAABZiaA=
From: "Claus Ibsen" <ci@silverbullet.dk>
To: <camel-user@activemq.apache.org>

BTW:

I have created a ticket: CAMEL-903 to fix the timestamp issue.

Bottom line:
Don't use timestamp comparison for matching new files. It's not reliable =
over the FTP protocol.


Med venlig hilsen
=20
Claus Ibsen
......................................
Silverbullet
Skovsg=E5rdsv=E6nget 21
8362 H=F8rning
Tlf. +45 2962 7576
Web: www.silverbullet.dk

-----Original Message-----
From: Claus Ibsen [mailto:ci@silverbullet.dk]=20
Sent: 15. september 2008 11:24
To: camel-user@activemq.apache.org
Subject: RE: Ftp consumer

Hi

Yes the ftp consumer uses by default timestamp for discovering new =
files. However timestamps on some (maybe most or all) FTP servers sent =
using the LIST command is not always precise to the second - only HH:MM =
(no seconds).

In that regard Camel is not that smart as it uses =
System.currentTimeMillis for "last run", and thus with bad luck could =
miss a file.

I don't encourage using this "timestamp" feature. For instance, if you =
restart Camel then it will set the timestamp to 0 and thus download all =
files again. Maybe I should write something about this on the wiki. Also =
timezone is not considered as well.

A different strategy is encouraged, such as renaming or deleting the =
files after download. These features are now provided in Camel 1.5 that =
however hasn't been released yet.


Med venlig hilsen
=20
Claus Ibsen
......................................
Silverbullet
Skovsg=E5rdsv=E6nget 21
8362 H=F8rning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-----Original Message-----
From: borgel [mailto:borge.lotre@gmail.com]=20
Sent: 15. september 2008 11:14
To: camel-user@activemq.apache.org
Subject: Ftp consumer


I have a route that polls a directory on a ftp server. The files are not
always downloaded. It seems like if I create a file locally and then =
waits a
while before uploading to the ftp server, the file is not consumed by =
Camel.
Could it be that the file don't get a new time stamp when uploaded and =
Camel
ignores it?

In Camel 1.5 there is a new property; consumer.deleteFile. If this is =
set to
true I think Camel should download and delete the file without looking =
at
the timestamp.=20


Btw: Great functionality in Camel 1.5 ftp and file handling!
--=20
View this message in context: =
http://www.nabble.com/Ftp-consumer-tp19489526s22882p19489526.html
Sent from the Camel - Users mailing list archive at Nabble.com.