camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bart Horré (JIRA) <>
Subject [jira] [Commented] (CAMEL-5829) File consumer - Allow to configure logging level of read lock strategy
Date Thu, 06 Jun 2013 11:52:24 GMT


Bart Horré commented on CAMEL-5829:

I took a stab at it, but since we're not able to disable logging programmatically via slf4j,
I saw no other option than providing a setter for readLockLoggingLevel on the GenericFileExclusiveReadLockStrategy
and check that value with an if clause before writing the log statement.

Not sure if this is a valid aproach
> File consumer - Allow to configure logging level of read lock strategy
> ----------------------------------------------------------------------
>                 Key: CAMEL-5829
>                 URL:
>             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:

View raw message