[
https://issues.apache.org/jira/browse/GEODE-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947194#comment-14947194
]
Kirk Lund commented on GEODE-189:
---------------------------------
This change requires further changes to GFSH because GFSH needs its own
log4j2.xml. Now that the default log4j2.xml is on the classpath, Log4J2 is
finding it and always using it.
Potential fixes:
1) move GFSH to its own JAR file with its own log4j2.xml in the root and change
GFSH scripts to move that JAR before the gemfire-core JAR
2) find an common way to specify log4j.configurationFile (Log4J2 requires a URL
which cannot be determined by the current GFSH scripts)
> 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)
