[
https://issues.apache.org/jira/browse/LOG4J2-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038008#comment-17038008
]
Ralph Goers edited comment on LOG4J2-2652 at 2/16/20 11:52 PM:
---------------------------------------------------------------
Using the sample application from Mike Waters I am able to see the failure in
the release-2.x branch and verify that the master branch is working fine. What
is very odd is when I convert the application to a unit test it does not
exhibit the problem in the release-2.x branch.
was (Author: ralph.go...@dslextreme.com):
Using the sample application from Mike Waters I am able to see the failure and
verify that the master branch is working fine. What is very odd is when I
convert the application to a unit test it does not exhibit the problem.
> JSON output wrong when using additonal fields
> ---------------------------------------------
>
> Key: LOG4J2-2652
> URL: https://issues.apache.org/jira/browse/LOG4J2-2652
> Project: Log4j 2
> Issue Type: Bug
> Components: Layouts
> Affects Versions: 2.12.0
> Reporter: Andreas Winter
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When using additional fields in the JsonLayout the output is something like
> {"logEvent":"File not found","source":"BIG","timestamp":"07-09-2019"}
> instead of the full JSON string as of version 2.10 (where everything works as
> expected).
> Config used:
>
> {code:java}
> <?xml version="1.0" encoding="UTF-8"?>
> <Configuration>
> <Appenders>
> <Console name="CONSOLE">
> <JsonLayout complete="false" compact="true" eventEol="true"
> stacktraceAsString="true">
> <KeyValuePair key="source" value="BIG"/>
> <KeyValuePair key="timestamp" value="$${date:MM-dd-yyyy}"/>
> </JsonLayout>
> </Console>
> </Appenders>
> <Loggers>
> <Root level="info">
> <AppenderRef ref="CONSOLE"/>
> </Root>
> </Loggers>
> </Configuration>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
