[
https://issues.apache.org/jira/browse/CAMEL-10839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132635#comment-17132635
]
shubhangi kaushal edited comment on CAMEL-10839 at 6/10/20, 6:54 PM:
---------------------------------------------------------------------
We are facing the same issue with SFTP consumers using pollenrich and
{{move=.done settings in Camel 2.24.1}}
[[email protected]] Is there any solution to avoid this log or alternative file
component to move files from parent directory to subdirectory?
was (Author: shubhangi.kaushal):
We are facing the same issue with SFTP consumers using pollenrich and
{{move=.done }}settings in Camel {{2.24.1}}
[[email protected]] Is there any solution to avoid this log or alternative file
component to move files from parent directory to subdirectory?
> SFTP consumer logs WARN stacktrace on every move to .camel
> ----------------------------------------------------------
>
> Key: CAMEL-10839
> URL: https://issues.apache.org/jira/browse/CAMEL-10839
> Project: Camel
> Issue Type: Bug
> Components: camel-ftp
> Affects Versions: 2.17.5, 2.18.2
> Reporter: Anthony Wood
> Priority: Minor
> Labels: logging
>
> The fix commited for CAMEL-10712 adds additional WARN-level logging with
> exception stack trace for a normally occurring situation: an SFTP consumer
> issuing a "delete" of {{.camel/$file}} prior to moving the consumed
> {{$file}} there.
> {{GenericFileProcessStrategySupport.renameFile()}} tries to delete the "to"
> file prior to renaming, and rightly ignores the exception when the file does
> not (yet) exist. However {{SftpOperations.deleteFile()}} was modified in
> CAMEL-10712 to {{LOG.warn(e)}} before rethrowing. This is a regression in
> the logging and generates much noise.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
