You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/10/01 18:42:00 UTC

[jira] [Commented] (GEODE-5799) Change log4j2.xml StatusLogger level to WARN

    [ https://issues.apache.org/jira/browse/GEODE-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634454#comment-16634454 ] 

ASF subversion and git services commented on GEODE-5799:
--------------------------------------------------------

Commit ac03101a34b5dc2c332d5391bc8e8519c4ca1673 in geode's branch refs/heads/develop from [~apache@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ac03101 ]

GEODE-5799: Set StatusLogger level to WARN (#2542)

This changes the level from FATAL to WARN. WARN is the default.

> Change log4j2.xml StatusLogger level to WARN
> --------------------------------------------
>
>                 Key: GEODE-5799
>                 URL: https://issues.apache.org/jira/browse/GEODE-5799
>             Project: Geode
>          Issue Type: Improvement
>          Components: logging
>            Reporter: Kirk Lund
>            Assignee: Kirk Lund
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Now that Geode is using HexThreadIdPatternConverter with unique plugin metadata, we can change the log4j2.xml configuration files in product and tests to have StatusLogger level of WARN instead of FATAL. This will allow us to see any new problems with our custom PatternConverters and Appenders earlier.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)