[
https://issues.apache.org/jira/browse/GEODE-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204075#comment-17204075
]
ASF subversion and git services commented on GEODE-8203:
--------------------------------------------------------
Commit d78f66c10eda48748ba6069050875da1222ae22b in geode's branch
refs/heads/support/1.13 from Jason Huynh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d78f66c ]
GEODE-8203: Provide ability to prevent disabling geode console appender (#5183)
(cherry picked from commit 4f559fc4d35ed4950faa083689e35a35c75eaa2f)
> Provide a way to prevent disabling logging to std out
> -----------------------------------------------------
>
> Key: GEODE-8203
> URL: https://issues.apache.org/jira/browse/GEODE-8203
> Project: Geode
> Issue Type: New Feature
> Components: logging
> Reporter: Jason Huynh
> Assignee: Jason Huynh
> Priority: Major
>
> It looks like when using geode by default
> disableLoggingToStandardOutputIfLoggingToFile is always called and std out is
> disabled if using the default log4j2.xml.
> The simplest options I can see are
> 1.) A mechanism to prevent disabling stdout, such as providing a system
> property
> 2.) Provide a gfsh command to re-enable the GeodeConsoleAppender
> We are unable to use the -Dlog4j.configurationFile because that property
> overrides the log4j configuration for all our other applications.
> We are also unable to override/extend the existing logging provider in our
> application (it's a non java app)
> This is not a request for changing default behavior. Just a request to
> provide a way to prevent auto disabling the std out appender.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
