The simple solution for me was to use subfolders instead of the root.
Still feels like a bug though.

Kind regards
/Gustav

-----Original Message-----
From: Gustav Sinder [mailto:gustav.sin...@ferrologic.se] 
Sent: den 9 september 2015 18:00
To: users@camel.apache.org
Subject: RE: Absolute path when moving done/error files on FTP server

I should have added that the Camel version we use is 2.15

Med vänlig hälsning / Kind regards
Gustav Sinder

-----Original Message-----
From: Gustav Sinder [mailto:gustav.sin...@ferrologic.se] 
Sent: den 9 september 2015 17:54
To: users@camel.apache.org
Subject: Absolute path when moving done/error files on FTP server

Hi,

I've got an issue with the ftp2/file2<ftp://ftp2/file2> component when fetching 
files from a remote FTP server and trying to move the handled files to a done 
subfolder.

Camel reports: 
org.apache.camel.component.file.GenericFileOperationFailedException: File 
operation failed:  Connection closed without indication.. Code: 350 The network 
guy on the other end reports that the FTP commands look strange and after a 
tcpdump inspection they sure do.

The endpoint is configured as follows:
ftp://user@host?password=password\&passiveMode=true\&consumer.delay=60000\&move=done\&moveFailed=error\&charset=utf-16\&include=MyFile\..*\.csv

My tcpdump inspection shows that Camel issues these commands when trying to 
move the file:
"Request: RNFR MyFile.csv"
"Request: RNTO //done/MyFile.csv"

Why do the component add the double slashes to the path that should be 
relative? Can I change my endpoint to change the behavior?
Tried using a ./done path instead but that gave: "Request: RNTO 
//./done/MyFile.csv"


Thanks

/Gustav

Reply via email to