[
https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660885#comment-16660885
]
Robert Ross commented on LOG4J2-2484:
-------------------------------------
This was stated in the requested use case:
_However, it is recognized that StatusLogger has the "chicken-or-egg" issue of
having to log messages prior to the Configuration being loaded._
If this is possible to get StatusLogger to output ALL of it's output to a
different stream with absolutely ZERO going to STDERR, I'm at a loss as to how
that is accomplished. No matter what I try to do programmatically, at least
some trace output goes to STDERR at startup prior to the configuration being
instantiated (either by file or by API).
> Allow setting of output stream on StatusLogger
> ----------------------------------------------
>
> Key: LOG4J2-2484
> URL: https://issues.apache.org/jira/browse/LOG4J2-2484
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Reporter: Robert Ross
> Priority: Minor
> Labels: StatusLogger, debugging
>
> The StatusLogger internally uses a SimpleLogger. SimpleLogger offers the
> ability to control the output stream, but StatusLogger encapsulates and hides
> this capability, always using System.err as the output stream.
> It would be useful to expose this option so that the API offers some control
> over the output stream used by StatusLogger.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
