[ https://issues.apache.org/jira/browse/CAMEL-11387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222198#comment-16222198 ]
Önder Sezgin commented on CAMEL-11387: -------------------------------------- today, i had a chance to test the case from windows client against unix ftp. {{stepwise=false}} does not seem to help. The problem is because the folder structure seems to get created on unix Server with Windows separators and jcraft's rename method needs '/' even if it is on windows. Sending PR soon. > SFTP is delivered into incorrect location, without exception (file in > subfolder + temp file is created + Camel running on Window & SFTP server > running on LINUX) > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: CAMEL-11387 > URL: https://issues.apache.org/jira/browse/CAMEL-11387 > Project: Camel > Issue Type: Bug > Components: camel-sftp > Affects Versions: 2.19.0 > Environment: camel is running on Window, and SFTP server is LINUX > Reporter: Cherry Ngai > Assignee: Önder Sezgin > Priority: Minor > Original Estimate: 168h > Remaining Estimate: 168h > > The bug only happens when: > i) file in subfolder > ii) temp file is created > iii) Camel running on Window & SFTP server running on LINUX > Route Configuration: > {code} > from("file://sourceFolder?recursive=true&delay=60000"). > to("sftp://username@linuxServer?tempFileName=${file:onlyname}.part"); > {code} > NOTES: added separator=UNIX or AUTO, I got the same issue. > Window Local File: sourceFolder/myfolder1/myfolder2/test.txt > FTPS Remote File Delivered: $linuxServer/myfolder1myfolder2test.txt > NOTES: > * There is no exception throw in 2.19.0, even though the file delivered into > incorrect location. > * In 2.17.3, exception throw at > org.apache.camel.component.file.remote.SftpOperations.renameFile(SftpOperations.java:431)[camel-ftp-2.17.3.jar:2.17.3] > * Without tempFileName, it works perfectly. Issue is around the rename area. -- This message was sent by Atlassian JIRA (v6.4.14#64029)