[jira] [Commented] (GEODE-8203) Provide a way to prevent disabling logging to std out

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GEODE-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124087#comment-17124087 ] 

ASF GitHub Bot commented on GEODE-8203:
---------------------------------------

jhuynh1 merged pull request #5183:
URL: https://github.com/apache/geode/pull/5183


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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)