[
https://issues.apache.org/jira/browse/LOG4J2-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17272232#comment-17272232
]
Carter Kozak commented on LOG4J2-3005:
--------------------------------------
[~sunshaowei] If you were able to fix the issue using the API differently,
could you post the original and fixed code in this ticket to help others who
encounter the same issue?
> log4j cannot correctly parse the input Message which contains {}
> ----------------------------------------------------------------
>
> Key: LOG4J2-3005
> URL: https://issues.apache.org/jira/browse/LOG4J2-3005
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.13.2
> Reporter: sunshaowei
> Priority: Major
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> the input string is \{"id":"123","name":{}}，if the value of name is empty，the
> called API
> *org.apache.logging.log4j.core.config.LoggerConfig#log(java.lang.String,
> java.lang.String, org.apache.logging.log4j.Marker,
> org.apache.logging.log4j.Level, org.apache.logging.log4j.message.Message,
> java.lang.Throwable)* will transfer the message to
> \{"id":"123","name":{id=123, name={}}}。so when after we called the API
> org.slf4j.spi.LocationAwareLogger#log，the output log is not the same as the
> input we expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
