org.springframework.beans.factory.NoSuchBeanDefinitionException解決方案

最新推荐文章于 2023-09-26 22:38:08 发布

放飞的承诺

最新推荐文章于 2023-09-26 22:38:08 发布

阅读量1.4k

点赞数

文章标签： java

本文链接：https://blog.csdn.net/u011684553/article/details/120196482

版权

这篇博客讨论了在SpringBoot2.x环境中，由于线程池配置不当导致的NoSuchBeanDefinitionException异常。异常信息显示在尝试获取名为'logs'的Executor bean时失败。解决方案在于确保配置的线程池名称与引用名称的一致性。博客深入解析了异常的根源，并提供了修复此类问题的具体步骤。

摘要由CSDN通过智能技术生成

环境：springboot 2.x
我这边引起的异常主要是多线程的线程池配置引起的
部分异常提示入下：

org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'logs' available: No matching Executor bean found for qualifier 'logs' - neither qualifier match nor bean name match!
	at org.springframework.beans.factory.annotation.BeanFactoryAnnotationUtils.qualifiedBeanOfType(BeanFactoryAnnotationUtils.java:136)
	at org.springframework.beans.factory.annotation.BeanFactoryAnnotationUtils.qualifiedBeanOfType(BeanFactoryAnnotationUtils.java:95)
	at org.springframework.aop.interceptor.AsyncExecutionAspectSupport.findQualifiedExecutor(AsyncExecutionAspectSupport.java:211)
	at org.springframework.aop.interceptor.AsyncExecutionAspectSupport.determineAsyncExecutor(AsyncExecutionAspectSupport.java:169)
	at org.springframework.aop.interceptor.AsyncExecutionInterceptor.invoke(AsyncExecutionInterceptor.java:107)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
	at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:747)
	at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:689)
	at org.com.annotations.AsyncLogs$$EnhancerBySpringCGLIB$$7368058.sqlOperaLogsSave(<generated>)