Shulou(Shulou.com)06/01 Report--

This article is to share with you what to do if there is a jar conflict in springboot integration log4j2. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Restart the springboot project and the following log appears:

SLF4J: Class path contains multiple SLF4J bindings.

SLF4J: Found binding in [jarVera fileVlGN dataRexProjectUniverse xxxMUSTAR startBinder.libOnOnLog4jMuslf4jFF4JUBUPUR 2.11.1.jarbank LF4jimplRandStaticLoggerBinder.class]

SLF4J: Found binding in [jarVera fileVlGUP dataRexProjectUniverse xxxMUSTAR startLIBGUBUBG logback LBINKE 1.2.3.JARMAX SLF4JUBINDUBINder.class]

SLF4J: Found binding in [jarVera fileVlGUP dataRexProjectUniverse xxx Mel startLIbUniBUR SLF4JUSIMPLUPUR 1.7.25.JARTHERGUBINDUBINDER]

SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]

Exception in thread "main" java.lang.StackOverflowError

At org.apache.logging.log4j.util.StackLocator.getCallerClass (StackLocator.java:110)

At org.apache.logging.log4j.util.StackLocator.getCallerClass (StackLocator.java:123)

At org.apache.logging.log4j.util.StackLocatorUtil.getCallerClass (StackLocatorUtil.java:55)

At org.apache.logging.slf4j.Log4jLoggerFactory.getContext (Log4jLoggerFactory.java:42)

At org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger (AbstractLoggerAdapter.java:46)

At org.apache.logging.slf4j.Log4jLoggerFactory.getLogger (Log4jLoggerFactory.java:29)

At org.slf4j.LoggerFactory.getLogger (LoggerFactory.java:358)

At org.apache.logging.slf4j.SLF4JLoggerContext.getLogger (SLF4JLoggerContext.java:39)

At org.apache.logging.slf4j.Log4jLoggerFactory.newLogger (Log4jLoggerFactory.java:37)

At org.apache.logging.slf4j.Log4jLoggerFactory.newLogger (Log4jLoggerFactory.java:29)

At org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger (AbstractLoggerAdapter.java:52)

At org.apache.logging.slf4j.Log4jLoggerFactory.getLogger (Log4jLoggerFactory.java:29)

At org.slf4j.LoggerFactory.getLogger (LoggerFactory.java:358)

At org.apache.logging.slf4j.SLF4JLoggerContext.getLogger (SLF4JLoggerContext.java:39)

At org.apache.logging.slf4j.Log4jLoggerFactory.newLogger (Log4jLoggerFactory.java:37)

At org.apache.logging.slf4j.Log4jLoggerFactory.newLogger (Log4jLoggerFactory.java:29)

At org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger (AbstractLoggerAdapter.java:52)

At org.apache.logging.slf4j.Log4jLoggerFactory.getLogger (Log4jLoggerFactory.java:29)

At org.slf4j.LoggerFactory.getLogger (LoggerFactory.java:358)

The problem can be solved by adding the following dependencies to pom

Org.springframework.boot

Spring-boot-starter

Org.springframework.boot

Spring-boot-starter-logging

Org.springframework.boot

Spring-boot-starter-log4j2

Configuration of the log4j2 file:

If you customize the file name, you need to configure it in application.yml

Logging:

Config: xxxx.xml

two。 The default name is log4j2-spring.xml, saving the configuration in application.yml

Thank you for reading! This is the end of the article on "what to do when there is a jar conflict in springboot integration log4j2". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it out for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.