[ https://issues.apache.org/jira/browse/GEODE-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125118#comment-17125118 ]
ASF subversion and git services commented on GEODE-8203: -------------------------------------------------------- Commit 71e40974d3a8053e5d0aa027004371a21495e3a3 in geode's branch refs/heads/develop from Jason Huynh [ https://gitbox.apache.org/repos/asf?p=geode.git;h=71e4097 ] GEODE-8203: Adding standard-output-always-on (#5200) * Added information about a new system property that prevents disabling logging to standard out when a log file is present > 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)