camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-8887) Exceptions on routes SFTP and SEDA or DISRUPTOR (probably others)
Date Fri, 19 Jun 2015 08:52:00 GMT

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

Claus Ibsen commented on CAMEL-8887:
------------------------------------

Use synchronous on the ftp endpoint, eg synchronous=true. You cannot have it async. Marking
methods as synchronous is not the solution.

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

Mime
View raw message