[
https://issues.apache.org/jira/browse/LOG4J2-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-898.
--------------------------------
Resolution: Fixed
Fixed in master in commit e1b70f6e.
If system property {{log4j.format.msg.async}} is set to {{true}}, log4j will no
longer call {{Message.getFormattedMessage()}} before passing the log event to
the background thread.
Note that in practice I suspect a fix for LOG4J2-772 is needed to see a
big(ger?) performance benefit. Patches welcome! :-)
Please verify and close.
> Format messages asynchronously
> ------------------------------
>
> Key: LOG4J2-898
> URL: https://issues.apache.org/jira/browse/LOG4J2-898
> Project: Log4j 2
> Issue Type: Improvement
> Affects Versions: 2.0.2, 2.1
> Reporter: Steven Grossman
> Assignee: Remko Popma
> Fix For: 2.5
>
>
> Formatting a message can be an expensive operation (e.g. String.format) and
> it is undesirable for it to be done in the calling thread when using an async
> logger or appender.
> LOG4J2-763 moved this work to the calling thread. Would you consider
> bringing back the previous behavior via a config/system property?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
