[
https://issues.apache.org/jira/browse/GEODE-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-1275:
-----------------------------
Description:
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 Manager 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 completely within our own classes without having
to add and remove custom Appender instances.
The code would then become simpler. Our custom code would not have to invoke
log4j2 core APIs and a User would have control over configuring our use of
log4j2 via the .xml file. Presently, a User cannot configure our AlertAppender
or LogWriterAppender in log4j2.xml.
was:
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 Manager 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 completely within our own classes without having
to add and remove custom Appender instances.
The code would then become much more simpler, our custom code would not have to
invoke log4j2 core APIs and a User would have fuller control over configuring
our use of log4j2 via the .xml file.
> Refactor custom appenders to move dynamic functionality into managers
> ---------------------------------------------------------------------
>
> Key: GEODE-1275
> URL: https://issues.apache.org/jira/browse/GEODE-1275
> Project: Geode
> Issue Type: Improvement
> Components: logging
> Reporter: Kirk Lund
>
> 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 Manager 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 completely within our own classes
> without having to add and remove custom Appender instances.
> The code would then become simpler. Our custom code would not have to invoke
> log4j2 core APIs and a User would have control over configuring our use of
> log4j2 via the .xml file. Presently, a User cannot configure our
> AlertAppender or LogWriterAppender in log4j2.xml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
