WARNINGs/ERRORs output with logback 1.1.7
See original GitHub issueFrom @Martin-Wegner…
Running the following config…
<encoder class="net.logstash.logback.encoder.LoggingEventCompositeJsonEncoder">
<providers>
<timestamp>
<fieldName>timestamp</fieldName>
</timestamp>
<logLevel>
<fieldName>logLevel</fieldName>
</logLevel>
<threadName>
<fieldName>threadName</fieldName>
</threadName>
<loggerName>
<fieldName>loggerName</fieldName>
</loggerName>
<callerData>
<classFieldName>className</classFieldName>
<methodFieldName >methodName</methodFieldName>
<fileFieldName>[ignore]</fileFieldName>
<lineFieldName>lineNumber</lineFieldName>
</callerData>
<message />
<stackTrace>
<fieldName>stackTrace</fieldName>
<throwableConverter class="net.logstash.logback.stacktrace.ShortenedThrowableConverter">
<exclude>java\..*</exclude>
<exclude>net\.sf\.cglib\..*</exclude>
<exclude>org\.springframework\..*</exclude>
<exclude>sun\..*</exclude>
<maxDepthPerThrowable>30</maxDepthPerThrowable>
<rootCauseFirst>true</rootCauseFirst>
</throwableConverter>
</stackTrace>
</providers>
</encoder>
produces the below errors with logback 1.1.7
Warning: Class 'net.logstash.logback.composite.loggingevent.LogLevelJsonProvider' contains multiple setters for the same property 'fieldNames'.
Warning: Class 'net.logstash.logback.composite.loggingevent.ThreadNameJsonProvider' contains multiple setters for the same property 'fieldNames'.
Warning: Class 'net.logstash.logback.composite.loggingevent.LoggerNameJsonProvider' contains multiple setters for the same property 'fieldNames'.
Warning: Class 'net.logstash.logback.composite.loggingevent.CallerDataJsonProvider' contains multiple setters for the same property 'fieldNames'.
Warning: Class 'net.logstash.logback.composite.loggingevent.MessageJsonProvider' contains multiple setters for the same property 'fieldNames'.
Warning: Class 'net.logstash.logback.composite.loggingevent.StackTraceJsonProvider' contains multiple setters for the same property 'fieldNames'.
20:50:41,230 |-ERROR in ch.qos.logback.core.joran.action.NestedBasicPropertyIA - Unexpected aggregationType AS_BASIC_PROPERTY_COLLECTION
20:50:41,230 |-ERROR in ch.qos.logback.core.joran.action.NestedBasicPropertyIA - Unexpected aggregationType AS_BASIC_PROPERTY_COLLECTION
20:50:41,231 |-ERROR in ch.qos.logback.core.joran.action.NestedBasicPropertyIA - Unexpected aggregationType AS_BASIC_PROPERTY_COLLECTION
20:50:41,231 |-ERROR in ch.qos.logback.core.joran.action.NestedBasicPropertyIA - Unexpected aggregationType AS_BASIC_PROPERTY_COLLECTION
Running the same configuration using logback 1.1.6 does not produce these warnings/errors
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:16 (1 by maintainers)
Top Results From Across the Web
WARNINGs/ERRORs output with logback 1.1.7 #160 - GitHub
These errors: Warning: Class 'net.logstash.logback.composite.loggingevent.LogLevelJsonProvider' contains multiple setters for the same property ...
Read more >How to prevent logback from outputting its own status at the ...
The deceptive thing about it is that the output seems to be outputting decisions made before it actually parses your logback file, (1>Could...
Read more >News - Logback - QOS.ch
ConsoleAppender now works with consoles confused by output strings of zero length, e.g. Java Web Start. ... 2016-03-29 Release of version 1.1.7.
Read more >Chapter 3: Logback configuration
We start by presenting ways for configuring logback, with many example configuration ... Thus, the output of the command java chapters.configuration.
Read more >Chapter 4: Appenders - Logback
It is responsible for outputting the logging events in a suitable format to the appropriate output device. Appenders are named entities.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Until these errors are fixed in logback, I can only recommend using logback 1.1.6
It looks like that logback is dead because of no activitiy since May 😦