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

Claus Ibsen commented on CAMEL-21947:
-------------------------------------

Yeah we will backport. I will look at to see if I can reuse your unit test. We 
can use a custom read lock that return false to simulate not started

> GenericFileConsumer with eager idempotence and read lock stop processing file
> -----------------------------------------------------------------------------
>
>                 Key: CAMEL-21947
>                 URL: https://issues.apache.org/jira/browse/CAMEL-21947
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-file, camel-ftp
>    Affects Versions: 4.8.6, 4.10.3, 4.11.0
>            Reporter: Håkan Lantz
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 4.12.0, 4.10.4, 4.8.7
>
>
> Hello,
> We have found a problem with the SftpConsumer (that applies for all file 
> cosumers).
> When it has been configured with "readLock=changed" and 
> "idempotentEager=true" the _GenericFileConsumer_ will in the _poll_ method:
>  # On the call to the _pollDirectory_ method store the idempotence key in the 
> idempotence repository (using the notUnique method)
>  # On the call to the _processBatch_ method it may fail to acquire a read 
> lock before the specified _readLockTimeout_ has been reached.
> When this occurs the file is silently left on the SFTP server and will not be 
> picked up.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to