[jira] [Assigned] (CAMEL-17213) camel-sftp `maximumReconnectAttempts` property changed behaviour

["Claus Ibsen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-17213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen reassigned CAMEL-17213:
-----------------------------------

    Assignee: Claus Ibsen

> camel-sftp `maximumReconnectAttempts` property changed behaviour
> ----------------------------------------------------------------
>
>                 Key: CAMEL-17213
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17213
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-sftp
>    Affects Versions: 3.13.0
>            Reporter: Mikołaj Matejko
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.14.0
>
>
> After upgrading from *Camel 3.11.3* to *Camel 3.13.0* we noticed that Camel cannot establish SFTP connection and throws an *`org.apache.camel.component.file.GenericFileOperationFailedException: Cannot connect to`* exception.
>  
> By diving into it we found out that the cause is `{*}maximumReconnectAttempts{*}` property which we had set to 0.
> before *Camel 3.13* -> *{{maximumReconnectAttempts}}* as the name says determined how many retries of connecting to sftp we should have (so setting it to 0 means we will try to connect once, and then we won’t try to reconnect in case of failure)
> in *Camel 3.13* -> *{{maximumReconnectAttempts}}* means how many connections to sftp we should have, so setting it to 0 means that we will never try to establish the connection 
> To solve this for now we changed *{{maximumReconnectAttempts}}* to 1, however we noticed that *SftpOperations.java* was refactored and probably this bug was unintentionally introduced, as it doesn't seem as correct behavior.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)