[
https://issues.apache.org/jira/browse/IGNITE-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945150#comment-15945150
]
ASF GitHub Bot commented on IGNITE-4863:
----------------------------------------
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/1687
IGNITE-4863: Log4jLogger can change RootLogger logging level unexpectedly.
…n other loggers.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4863
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1687.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 #1687
----
commit dedbdfaa1c34890484ff184d77612716fb340ff1
Author: Andrey V. Mashenkov <[email protected]>
Date: 2017-03-28T13:22:57Z
Disallow change RootLogger log-level if it can have negative effect on
other loggers.
----
> Log4jLogger can change RootLogger logging level unexpectedly.
> -------------------------------------------------------------
>
> Key: IGNITE-4863
> URL: https://issues.apache.org/jira/browse/IGNITE-4863
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 1.5.0.final
> Reporter: Andrew Mashenkov
> Assignee: Andrew Mashenkov
>
> Setting System property "IGNITE_CONSOLE_APPENDER" to true will set rootLogger
> level to OFF that can be unexpectedly as well.
> See
> http://apache-ignite-users.70518.x6.nabble.com/Logging-ignite-log4j-jar-td11400.html
> Seems, we should check if there is no other loggers configured which can
> inherits rootLogger logging level before raising level or turning rootLogger
> off.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
