[
https://issues.apache.org/jira/browse/GEODE-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-2644:
-----------------------------
Labels: AlertAppender Log4j2 LogWriterAppender log4j2.xml (was:
AlertAppender Log4j2 LogWriterAppender)
> 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: logging
> Reporter: Kirk Lund
> Labels: AlertAppender, Log4j2, LogWriterAppender, log4j2.xml
>
> Presently Geode adds and configures the LogWriterAppender and AlertAppender
> at runtime. These appenders cannot be specified or configured within xml.
> This is a request to change Geode so that these appenders can be specified
> and configured in a custom log4j2.xml file.
> This ticket requires GEODE-1275. Right now these appenders are added and
> removed by Geode when connecting or disconnecting from the DistributedSystem.
> When these appenders were introduced, this behavior was required to maintain
> previous behavior. If we refactor the appenders to add one more layer of
> indirection between the appender and the DS lifecycle, then this internal
> layer could enable/disable active appending even when the appenders are
> specified within log4j2.xml.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
