Hi Laurentiu Trica, 1, you may want to use the exclude option, eg: ?move=/in/archive&exclude=/in/archive/* 2, on different systems, readLock's behavior may vary, the one that I find works most of the time on linux is "changed". If that still does not work, you can try to have your own exclusiveReadLockStrategy
Regards, Ngoc Hai --- On Thu, 5/12/11, Laurentiu Trica <[email protected]> wrote: > From: Laurentiu Trica <[email protected]> > Subject: Camel FTP poller issue > To: "Camel" <[email protected]> > Date: Thursday, May 12, 2011, 9:19 PM > Hi, > > I've been using the FTP poller for some time now in > production environment > and I keep having couple problems with it: > > 1) because I'm using an archive folder, it happens that a > file cannot be > moved after being processed from, let's say /in folder to > /in/archive > folder. And this, somehow, triggers the creation of another > in folder with a > archive subfolder. > Just to be clear: > Initial folder structure: > /in > /archive > > The structure after the error: > /in > archive > in > /archive > > Seems like some operation is duplicating the folder > structure. > > 2) It happens for a file to be processed several times > Anything goes ok, but for no reason at all, the file is > processed three or > more times. I suspect it has to do with not being to move > the file to the > /archive folder but I'm not sure. > > 3) It happens for a file to not be read entirely. Maybe it > was read while > being written to the FTP account. I know that the readLock > option should > work on the FTP if used with the rename strategy but this > seems not to work. > > Had any of you similar problems? > > I'll provide some logging as soon as possible. > > Thank you for your time, > Laurentiu Trica >
