[ https://issues.apache.org/jira/browse/GEODE-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16690089#comment-16690089 ]
ASF subversion and git services commented on GEODE-2644: -------------------------------------------------------- Commit 145276390ed69cbee715f12c069116e6f2720b5d in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1452763 ] GEODE-2644: Cleanup logging related files Cleanup files that helped fix logging related test failures or helped with reviewing and understanding code while working on GEODE-2644. * Remove warnings and improve code cleanliness * Improve testing and failure messages > Provide ability to configure Geode appenders in log4j2.xml > ---------------------------------------------------------- > > Key: GEODE-2644 > URL: https://issues.apache.org/jira/browse/GEODE-2644 > Project: Geode > Issue Type: Improvement > Components: configuration, logging > Reporter: Kirk Lund > Assignee: Kirk Lund > Priority: Major > Labels: AlertAppender, Log4j2, LogWriterAppender, log4j2.xml, > pull-request-available > Fix For: 1.9.0 > > Time Spent: 8h 10m > Remaining Estimate: 0h > > Presently Geode dynamically creates, adds and removes AlertAppender and > LogWriterAppender by manipulating log4j2 core API. We should move the bulk of > the Appender functionality to internal classes and just leave the Appenders > registered with log4j2 during the life of the JVM. > This allows us to enable and configure our Appenders via log4j2.xml and > control the Cache-controlled lifecycle internally without having to add and > remove custom Appender instances. > The code would then become simpler, we could avoid invoking log4j2 core APIs, > and users would have control over configuring our use of log4j2 completely > within the .xml file. Presently, a user cannot configure our AlertAppender or > LogWriterAppender in log4j2.xml. -- This message was sent by Atlassian JIRA (v7.6.3#76005)