[
https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326812#comment-15326812
]
Remko Popma edited comment on LOG4J2-1395 at 6/13/16 4:39 AM:
--------------------------------------------------------------
Strange. I built the project again and got the same error with the new jar.
I then tried to investigate by setting status="trace" in the configuration file
and rebuilt, and then it started working... Not sure what is going on.
Performance-wise this seems significantly faster though. I have no objection to
adding this option. Stability is important, so it may be a good idea to keep
the current option as the default.
was (Author: [email protected]):
Strange. I built the project again and got the same error with the new jar.
I then tried to investigate by setting status="trace" in the configuration file
and rebuilt, and then it started working... Not sure what is going on.
> Faster Console appender
> -----------------------
>
> Key: LOG4J2-1395
> URL: https://issues.apache.org/jira/browse/LOG4J2-1395
> Project: Log4j 2
> Issue Type: Improvement
> Components: Appenders
> Affects Versions: 2.5, 2.6, 2.6.1
> Reporter: Mikael Ståldal
> Attachments: ggregory-hardware.txt
>
>
> The ConsoleAppender is much slower than the FileAppender.
> It would be nice to improve the performance of the ConsoleAppender.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
