[
https://issues.apache.org/jira/browse/LOG4J2-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020401#comment-17020401
]
Art Licis edited comment on LOG4J2-1475 at 1/21/20 5:30 PM:
------------------------------------------------------------
This issue was created against v 2.6. For that version, it wasn't possible to
prevent this lookup functionality.
However, since version 2.7 it's possible to avoid this by using %m\{nolookups}
pattern.
And version 2.10 introduced log4j2.formatMsgNoLookups setting which is false by
default, but can be changed to true to globally avoid lookups in messages.
Hence this issue could be resolved. However, as a user, I wouldn't expect any
lookups in the the plain message I'm logging.
was (Author: art-licis):
This issue was created against v 2.6. For that version, it wasn't possible to
prevent this lookup functionality.
However, since version 2.7 it's possible to avoid this by using %m\{nolookups}
pattern.
And version 2.10 introduced log4j2.formatMsgNoLookups setting which is false by
default, but can be changed to true to globally avoid lookups in messages.
> High CPU utilization if large log message contains '${'
> -------------------------------------------------------
>
> Key: LOG4J2-1475
> URL: https://issues.apache.org/jira/browse/LOG4J2-1475
> Project: Log4j 2
> Issue Type: Bug
> Components: Layouts, Pattern Converters
> Affects Versions: 2.6.2
> Environment: JDK 7u80
> Reporter: Hikaru Abe
> Priority: Minor
> Attachments: dollar-braces.txt, log4j2.xml
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
