You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/06/19 10:52:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Claus Ibsen updated CAMEL-8887:
-------------------------------
    Priority: Minor  (was: Critical)

> 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: Minor
>
> 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)