[
https://issues.apache.org/jira/browse/GEODE-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632235#comment-16632235
]
ASF subversion and git services commented on GEODE-2644:
--------------------------------------------------------
Commit 076fff86683d3f2ed14c978dd5ba4c3031ae6a64 in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=076fff8 ]
GEODE-2644: Improve GfshParserAutoCompletionTest assertions (#2534)
Improve assertions so that failures in this test can be diagnosed without
using the IDE debugger.
> 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
> Time Spent: 4.5h
> 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)
