[
https://issues.apache.org/jira/browse/CAMEL-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667947#comment-13667947
]
Nerses Aznauryan commented on CAMEL-5829:
-----------------------------------------
Hi Claus,
What about FtpChangedExclusiveReadLockStrategy and
SftpChangedExclusiveReadLockStrategy. I think they should have them as well. If
so we can add the option to GenericFileExclusiveReadLockStrategy interface.
> File consumer - Allow to configure logging level of read lock strategy
> ----------------------------------------------------------------------
>
> Key: CAMEL-5829
> URL: https://issues.apache.org/jira/browse/CAMEL-5829
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.12.0, Future
>
>
> The read lock strategy may log at WARN level if they cannot acquire a read
> lock on a file. Some ppl may want to lower this level to not have this in
> their logs.
> {code}
> WARN |
> org.apache.camel.component.file.strategy.FileChangedExclusiveReadLockStrategy
> | Cannot acquire read lock within 60000 millis. Will skip the file:
> GenericFile[\Projects\xxx\somefile.txt] -
> {code}
> We should add a new option which can be set on the read lock strategies. Just
> like you can set the timeout value.
> || Option || Default || Description ||
> |readLockLoggingLevel | WARN | *Camel 2.11:* Logging level used when a read
> lock could *not* be acquired. By default a WARN is logged. You can change
> this level, for example to OFF to not have any logging. This option is only
> applicable for readLock of types: changed, fileLock, rename |
> This option is only applicable for
> - FileChangedExclusiveReadLockStrategy
> - FileLockExclusiveReadLockStrategy
> - GenericFileRenameExclusiveReadLockStrategy
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
