You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Gwenhaël PASQUIERS (JIRA)" <ji...@apache.org> on 2015/06/19 10:49:00 UTC
[jira] [Commented] (CAMEL-8887) Exceptions on routes SFTP and SEDA
or DISRUPTOR (probably others)
[ https://issues.apache.org/jira/browse/CAMEL-8887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593207#comment-14593207 ]
Gwenhaël PASQUIERS commented on CAMEL-8887:
-------------------------------------------
Link to the related discussion on the maling list archive (nabble)
http://camel.465427.n5.nabble.com/sftp-gt-seda-yields-GenericFileOperationFailedException-during-GenericFileOnCompletion-move-processig-td2905598.html
> Exceptions on routes SFTP and SEDA or DISRUPTOR (probably others)
> -----------------------------------------------------------------
>
> Key: CAMEL-8887
> URL: https://issues.apache.org/jira/browse/CAMEL-8887
> Project: Camel
> Issue Type: Bug
> Components: camel-ftp
> Environment: Camel running on Windows, polling Linux server.
> Reporter: Gwenhaël PASQUIERS
> Priority: Critical
>
> When polling from SFTP, if the exchanges are sent to asynchronous routes (seda, disruptor) many different types of exceptions happen everytime, when retrienving the content or deleting / moving / renaming the polled files.
> The cause is that when routes are executed asynchronously, concurrent calls to SftpOperations are made. It looks like SftpOperations as well as ChannelSftp (Jsch) are not thread-safe. Sftp commands are either colliding, and sometime are invalid at the protocol level.
> One workaround is to make SftpOperations thread-safe by making its methods synchronized.
> Maybe there is another better place for a fix but i leave that to the specialists.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)