geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <>
Subject [jira] [Commented] (GEODE-2644) Provide ability to configure Geode appenders in log4j2.xml
Date Tue, 20 Aug 2019 19:07:01 GMT


ASF subversion and git services commented on GEODE-2644:

Commit 63034887c70e7bb7ec5e086b5154b626049a84c0 in geode's branch refs/heads/release/1.9.1
from Kirk Lund
[;h=6303488 ]

GEODE-7058: Mark log4j-core optional in geode-core

Note: this change requires all commits from GEODE-2644 and GEODE-6122.
(cherry picked from commit 413800bc16d05df689a2af5c30797f180aad6088)

> Provide ability to configure Geode appenders in log4j2.xml
> ----------------------------------------------------------
>                 Key: GEODE-2644
>                 URL:
>             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
> 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

View raw message