[ 
https://issues.apache.org/jira/browse/CAMEL-10841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869631#comment-15869631
 ] 

Stephan Siano commented on CAMEL-10841:
---------------------------------------

unfortunately the deleteFile calls are spread all over the camel-file and the 
camel-ftp components, so changing the way exceptions are thrown for this issue 
is not reasonable.

I will just reduce the log level for the log to debug. This will normally not 
fill up the log with confusing entries, but will make it possible to analyze 
issues if they occur. Other similar issues (e.g. when creating directories) are 
also logged with debug in the file component.

> Move operation will create a warning log message
> ------------------------------------------------
>
>                 Key: CAMEL-10841
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10841
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-ftp
>    Affects Versions: 2.17.5, 2.18.2
>            Reporter: Stephan Siano
>            Assignee: Stephan Siano
>            Priority: Minor
>
> I'm using an enpoint like this one : 
>  - 
> sftp://myserver/folder1/folder2?idempotent=true&stepwise=false&...&move=../archive
>  
> With 2.18.2, I have logs like this : 
> {noformat}
>   2017-02-15T13:23:47.314 [Camel (camel-1) thread #10 - 
> sftp://myserver/folder1/folder2] WARN  o.a.c.c.file.remote.SftpOperations - 
> Cannot delete file: folder1/folder2/../archive/myfile.txt
> com.jcraft.jsch.SftpException: No such file
>       at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2873)
>       at com.jcraft.jsch.ChannelSftp.rm(ChannelSftp.java:1985)
>       at 
> org.apache.camel.component.file.remote.SftpOperations.deleteFile(SftpOperations.java:435)
>       at 
> org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:100)
> {noformat}
> the issue was introduced with CAMEL-10712



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to