[
https://issues.apache.org/jira/browse/CAMEL-11601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101903#comment-16101903
]
ASF GitHub Bot commented on CAMEL-11601:
----------------------------------------
GitHub user valdar opened a pull request:
https://github.com/apache/camel/pull/1851
[CAMEL-11601] : change camel-file default value for readLockLoggingLe…
…vel from WARN to DEBUG
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/valdar/camel CAMEL-11601
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1851.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1851
----
commit fc4dc8020901e8924526182f2d1492a2b8540746
Author: Andrea Tarocchi <[email protected]>
Date: 2017-07-26T16:35:51Z
[CAMEL-11601] : change camel-file default value for readLockLoggingLevel
from WARN to DEBUG
----
> change camel-file default value for readLockLoggingLevel from WARN to DEBUG
> ---------------------------------------------------------------------------
>
> Key: CAMEL-11601
> URL: https://issues.apache.org/jira/browse/CAMEL-11601
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Andrea Tarocchi
> Priority: Minor
>
> The default value setted at {{WARN}} for {{readLockLoggingLevel}} seems a
> little bit aggressive for just not being able to acquire a read lock (there
> are quite legitimate situations in which this can happen and is not a problem
> at all but just the intended way of working), would be better to change it
> {{DEBUG}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
