[
https://issues.apache.org/jira/browse/GEODE-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-189:
----------------------------
Comment: was deleted
(was: Yes, a user can override the Geode log4j2.xml by either having their own
log4j2.xml earlier in the classpath (before the gemfire core jar) or by
specifying log4j.configurationFile.)
> Configure log4j2 on classpath instead of with system property
> -------------------------------------------------------------
>
> Key: GEODE-189
> URL: https://issues.apache.org/jira/browse/GEODE-189
> Project: Geode
> Issue Type: Bug
> Affects Versions: 1.0.0-incubating
> Reporter: Kirk Lund
> Assignee: Kirk Lund
> Fix For: 1.0.0-incubating
>
>
> This change is necessary for GEODE-77. It's easier to complete on its own
> feature branch and then be cherry-picked over to feature/GEODE-77.
> Geode configures Log4J2 using a system property, however, if a configuration
> file is already found on the classpath then it will defer configuration to
> that file. The new JGroups jar contains a log4j2.xml config file in its root,
> so Log4J2 finds it on the classpath and always uses it instead of Geode's
> log4j2-default.xml.
> This change would involve moving Geode's log4j2-default.xml to the root of
> the gemfire-core jar file and rename it to log4j2.xml. The gemfire-core jar
> would then be placed earlier on the classpath than the jgroups jar so that
> the default configuration of Geode prefers the one in the gemfire-core jar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
