✨重磅！盹猫的个人小站正式上线啦～诚邀各位技术大佬前来探秘！✨
这里有：
- 硬核技术干货：编程技巧、开发经验、踩坑指南，带你解锁技术新姿势！
- 趣味开发日常：代码背后的脑洞故事、工具测评，让技术圈不再枯燥～
- 独家资源分享：开源项目、学习资料包，助你打怪升级快人一步！
👉 点击直达→ 盹猫猫的个人小站 👈
🌟 来逛逛吧，说不定能挖到你正在找的技术宝藏哦～
目录
欢迎来到盹猫的博客
本篇文章主要介绍了
[关于"LoggerFactory is not a Logback LoggerContext but Logback is on ......"的解决方案]
❤博主广交技术好友，喜欢文章的可以关注一下❤
📅 日期：2025-07-30
🔧 技术栈：Spring Boot 2.x / JDK 8
🏷️ 标签：#Java #BugFix #SpringBoot #Debug
1. 🐛 错误现象
报错信息（关键部分）
在引入百度短信调用SDK依赖以后
<dependency>
<groupId>com.baidubce</groupId>
<artifactId>bce-java-sdk</artifactId>
<version>0.10.362</version>
</dependency>运行时出现下述错误.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/seaua/.m2/repository/org/apache/logging/log4j/log4j-slf4j-impl/2.15.0/log4j-slf4j-impl-2.15.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/seaua/.m2/repository/ch/qos/logback/logback-classic/1.2.11/logback-classic-1.2.11.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/seaua/.m2/repository/org/slf4j/slf4j-reload4j/1.7.36/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/seaua/.m2/repository/org/slf4j/slf4j-simple/1.7.36/slf4j-simple-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
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 "restartedMain" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.boot.devtools.restart.RestartLauncher.run(RestartLauncher.java:49)
Caused by: java.lang.IllegalArgumentException: LoggerFactory is not a Logback LoggerContext but Logback is on the classpath. Either remove Logback or the competing implementation (class org.apache.logging.slf4j.Log4jLoggerFactory loaded from file:/home/seaua/.m2/repository/org/apache/logging/log4j/log4j-slf4j-impl/2.15.0/log4j-slf4j-impl-2.15.0.jar). If you are using WebLogic you will need to add 'org.slf4j' to prefer-application-packages in WEB-INF/weblogic.xml: org.apache.logging.slf4j.Log4jLoggerFactory
at org.springframework.util.Assert.instanceCheckFailed(Assert.java:702)
at org.springframework.util.Assert.isInstanceOf(Assert.java:621)
at org.springframework.boot.logging.logback.LogbackLoggingSystem.getLoggerContext(LogbackLoggingSystem.java:294)
at org.springframework.boot.logging.logback.LogbackLoggingSystem.beforeInitialize(LogbackLoggingSystem.java:118)
at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationStartingEvent(LoggingApplicationListener.java:238)
at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:220)
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176)
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:131)
at org.springframework.boot.context.event.EventPublishingRunListener.starting(EventPublishingRunListener.java:79)
at org.springframework.boot.SpringApplicationRunListeners.lambda$starting$0(SpringApplicationRunListeners.java:56)
at java.util.ArrayList.forEach(ArrayList.java:1259)
at org.springframework.boot.SpringApplicationRunListeners.doWithListeners(SpringApplicationRunListeners.java:120)
at org.springframework.boot.SpringApplicationRunListeners.starting(SpringApplicationRunListeners.java:56)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:298)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1303)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1292)
at com.uav.BootApplication.main(BootApplication.java:14)
... 5 more
进程已结束,退出代码0
复现步骤
使用排除法,引入该依赖或注释掉该pom依赖进行程序运行来判断是否是该依赖引起的问题.
2. 🔍 问题分析
可能的原因
出现问题后首先看一下主要的报错翻译,内容如下:
java.lang.IllegalArgumentException：LoggerFactory 不是 Logback LoggerContext，但类路径中包含 Logback。请移除 Logback 或其竞争实现（从文件:/home/seaua/.m2/repository/org/apache/logging/log4j/log4j-slf4j-impl/2.15.0/log4j-slf4j-impl-2.15.0.jar 加载的类 org.apache.logging.slf4j.Log4jLoggerFactory）。如果您使用的是 WebLogic，则需要在 WEB-INF/weblogic.xml 的 prefer-application-packages 中添加“org.slf4j”：org.apache.logging.slf4j.Log4jLoggerFactory
这里提到了移除Logback和slf4j,则可能是Logback与其它日志依赖代码冲突,导致启动时不知道使用哪个类.
3. 🛠️ 解决方案
修复代码
对存在问题的依赖进行移除,保证代码正常运行.
修复前依赖（问题代码）
<dependency>
<groupId>com.baidubce</groupId>
<artifactId>bce-java-sdk</artifactId>
<version>0.10.362</version>
</dependency>修复后依赖（安全代码）
<dependency>
<groupId>com.baidubce</groupId>
<artifactId>bce-java-sdk</artifactId>
<version>0.10.362</version>
<exclusions>
<exclusion>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-core</artifactId>
</exclusion>
<exclusion>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
</exclusion>
</exclusions>
</dependency>4. 📚 经验总结
该错误主要容易出现在引入过多三方依赖的情况下,由于不同公司使用的日志依赖版本不同,而导致的版本冲突问题,在排除冲突依赖后,程序可以正常启动还有就是一定要从报错中发现问题,直接翻译一下就基本可以定位问题所在.
📢 你的代码里有没有类似的坑？欢迎评论区讨论！ 🚀
🔗 相关资源
如果你对区块链内容感兴趣可以查看我的专栏:小试牛刀-区块链
✍️ 作者：盹猫
📅 最后更新：2025-07-30
🔔 关注我，获取更多技术干货！ 🚀
