You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Owen Nichols (Jira)" <ji...@apache.org> on 2020/09/29 16:26:00 UTC
[jira] [Updated] (GEODE-8203) Provide a way to prevent disabling
logging to std out
[ https://issues.apache.org/jira/browse/GEODE-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen Nichols updated GEODE-8203:
--------------------------------
Fix Version/s: 1.13.1
1.14.0
> 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
> Fix For: 1.14.0, 1.13.1
>
>
> 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)