[
https://issues.apache.org/jira/browse/LOG4J2-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862677#comment-15862677
]
Ralph Goers commented on LOG4J2-1812:
-------------------------------------
I had always intended to have the capability to dump the ring buffer, but doing
it automatically needs to be done carefully as it could lead to more confusion.
For example, instead of adding the "Set system property" text you could add -
"The previous n status messages are:" followed by the previous n status
messages.
> Improve error message when log4j 2 configuration file not found
> ---------------------------------------------------------------
>
> Key: LOG4J2-1812
> URL: https://issues.apache.org/jira/browse/LOG4J2-1812
> Project: Log4j 2
> Issue Type: Improvement
> Components: Configurators
> Affects Versions: 2.3, 2.4, 2.5, 2.6, 2.7, 2.8
> Reporter: Remko Popma
> Assignee: Remko Popma
> Fix For: 2.8.1
>
>
> When configuration fails because no Log4j 2 configuration file is found, the
> following message is logged to the console at ERROR level:
> {code}
> No log4j2 configuration file found. Using default configuration: logging only
> errors to the console.
> {code}
> We should be able to improve this. One idea is to add this:
> {code}
> No log4j2 configuration file found. Using default configuration: logging only
> errors to the console. Set system property
> 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show
> Log4j2 internal initialization logging.
> {code}
> Another idea is to dump the contents of the StatusLogger ring buffer to the
> console.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
