Due to a break in compatibility in the slf4j binding, as of release 2.11.1 two. This typically happens when both `log4j. It uses logback by default.
org.apache.logging.log4j.LoggingException log4jslf4jimpl cannot be
Due to a break in compatibility in the slf4j binding, as of release 2.19.0 two slf4j to log4j adapters are provided.
I'm using spring boot without further logging libraries.
[warning] corrupted stdout by directly writing to native stream in forked jvm 1. According to spring boot documentation, you should. My guess is there is no transitive dependency involved that is responsible for this problem. The result is the usage of standard logging or in other words ignoring my.
Reading online and asking around it seems the issue was this file: Update your web.xml to use the log4j 2.x.
