You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2017/04/06 11:30:42 UTC

[jira] [Updated] (IGNITE-4863) Log4jLogger can change RootLogger logging level unexpectedly.

     [ https://issues.apache.org/jira/browse/IGNITE-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Mashenkov updated IGNITE-4863:
-------------------------------------
    Fix Version/s: 2.0

> 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
>             Fix For: 2.0
>
>
> 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)