Spring循环引用-@Async注解启动报错，而@Transactional则不会

最新推荐文章于 2023-04-19 15:55:36 发布
最新推荐文章于 2023-04-19 15:55:36 发布
阅读量1k 收藏 2
点赞数
文章标签： spring java 后端
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/liangbo7/article/details/122021114
版权

目录

一、问题描述

二、问题分析

1、代理类

2、代理过程

 三、结论

上接《Spring循环引用-@Async注解启动报错分析》

一、问题描述

Bean1Service注解@Async

启动报错 


  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::                (v2.4.1)

2021-12-19 11:16:45.271  INFO 168 --- [           main] com.lb.reference.ReferenceApplication    : Starting ReferenceApplication using Java 1.8.0_191 on DESKTOP-58VVQ1F with PID 168 (D:\java\ws_1\cycle-reference\target\classes started by liangbo in D:\java\ws_1\cycle-reference)
2021-12-19 11:16:45.276  INFO 168 --- [           main] com.lb.reference.ReferenceApplication    : No active profile set, falling back to default profiles: default
2021-12-19 11:16:46.850  INFO 168 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8090 (http)
2021-12-19 11:16:46.865  INFO 168 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2021-12-19 11:16:46.865  INFO 168 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.41]
2021-12-19 11:16:46.949  INFO 168 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2021-12-19 11:16:46.949  INFO 168 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 1608 ms
2021-12-19 11:16:47.050  WARN 168 --- [           main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'bean1Service': Bean with name 'bean1Service' has been injected into other beans [bean2Service] in its raw version as part of a circular reference, but has eventually been wrapped. This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesForType' with the 'allowEagerInit' flag turned off, for example.
2021-12-19 11:16:47.055  INFO 168 --- [           main] o.apache.catalina.core.StandardService   : Stopping service [Tomcat]
2021-12-19 11:16:47.202  INFO 168 --- [           main] ConditionEvaluationReportLoggingListener : 

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2021-12-19 11:16:47.263 ERROR 168 --- [           main] o.s.boot.SpringApplication               : Application run failed

org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'bean1Service': Bean with name 'bean1Service' has been injected into other beans [bean2Service] in its raw version as part of a circular reference, but has eventually been wrapped. This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesForType' with the 'allowEagerInit' flag turned off, for example.
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:638) ~[spring-beans-5.3.2.jar:5.3.2]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:531) ~[spring-beans-5.3.2.jar:5.3.2]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335) ~[spring-beans-5.3.2.jar:5.3.2]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-5.3.2.jar:5.3.2]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333) ~[spring-beans-5.3.2.jar:5.3.2]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208) ~[spring-beans-5.3.2.jar:5.3.2]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:944) ~[spring-beans-5.3.2.jar:5.3.2]
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:923) ~[spring-context-5.3.2.jar:5.3.2]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:588) ~[spring-context-5.3.2.jar:5.3.2]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:144) ~[spring-boot-2.4.1.jar:2.4.1]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:767) [spring-boot-2.4.1.jar:2.4.1]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:759) [spring-boot-2.4.1.jar:2.4.1]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:426) [spring-boot-2.4.1.jar:2.4.1]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:326) [spring-boot-2.4.1.jar:2.4.1]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1309) [spring-boot-2.4.1.jar:2.4.1]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1298) [spring-boot-2.4.1.jar:2.4.1]
	at com.lb.reference.ReferenceApplication.main(ReferenceApplication.java:13) [classes/:na]

Bean1Service注解@Async改@Transactional

 启动正常


  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::                (v2.4.1)

2021-12-19 10:40:12.879  INFO 11056 --- [           main] com.lb.reference.ReferenceApplication    : Starting ReferenceApplication using Java 1.8.0_191 on DESKTOP-58VVQ1F with PID 11056 (D:\java\ws_1\cycle-reference\target\classes started by liangbo in D:\java\ws_1\cycle-reference)
2021-12-19 10:40:12.883  INFO 11056 --- [           main] com.lb.reference.ReferenceApplication    : No active profile set, falling back to default profiles: default
2021-12-19 10:40:14.363  INFO 11056 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8090 (http)
2021-12-19 10:40:14.376  INFO 11056 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2021-12-19 10:40:14.377  INFO 11056 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.41]
2021-12-19 10:40:14.460  INFO 11056 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2021-12-19 10:40:14.460  INFO 11056 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 1506 ms
2021-12-19 10:40:14.728  INFO 11056 --- [           main] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService 'applicationTaskExecutor'
2021-12-19 10:40:15.437  INFO 11056 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8090 (http) with context path ''
2021-12-19 10:40:15.460  INFO 11056 --- [           main] com.lb.reference.ReferenceApplication    : Started ReferenceApplication in 3.1 seconds (JVM running for 3.785)

二、问题分析

1、代理类

@Async生成代理逻辑是后置处理器放org.springframework.scheduling.annotation.AsyncAnnotationBeanPostProcessor.postProcessAfterInitialization(Object, String)；在实例化之后就生成代理对象；

@Transactional生成代理逻辑是后置处理器方法org.springframework.aop.framework.autoproxy.InfrastructureAdvisorAutoProxyCreator.getEarlyBeanReference(Object, String)；在获取提前暴露的引用时就生成代理对象。

2、代理过程

（1）、bean1在创建过程中，提前暴露引用工厂类加入三级缓存singletonFactories。

 

 （2）、执行至方法org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(String, RootBeanDefinition, BeanWrapper)时，由于依赖bean2，此时bean2还没初始化，就像bean1一样进行初始化。

 

（3）、又由于bean2依赖bean1，初始化执行方法org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(String, RootBeanDefinition, BeanWrapper)时，进行属性bean1填充，调用获取bean1的方法org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(String)，该方法从三级缓存singletonFactories工厂生成bean1实例，其中方法org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.getEarlyBeanReference(String, RootBeanDefinition, Object)调用实现SmartInstantiationAwareBeanPostProcessor接口类的方法getEarlyBeanReference进行生成事务代理对象。

 （4）、生成事务代理类InfrastructureAdvisorAutoProxyCreator实现了SmartInstantiationAwareBeanPostProcessor，刚好代理逻辑在getEarlyBeanReference方法中，所以bean2的属性bean1已经是代理后的对象；而生成异步代理类AsyncAnnotationBeanPostProcessor只是实现BeanPostProcessor，代理逻辑在postProcessAfterInitialization方法。

 

 （5）、初始化完bean2后，返回接着初始化bean1，方法initalizeBean没有对bean1事务代理进行包装，故exposedObject == bean成立；而方法initalizeBean会对bean1生成异步代理对象，故exposedObject != bean。

 三、结论

@Async和@Transational代理都是动态代理，在循环引用时，初始化表现有差异，是代理位置不一致造成的

liangbo7
关注
Spring @Async 注解多线程导致Spring的注解@Transactional失效问题
ssmaaa的博客
02-20 3731
本文Spring @Async 注解多线程导致Spring的注解@Transactional失效与多数据源切换问题！ 问题：多线程为什么会导致事务注解@Transactional失效 实现AOP的方法有动态代理、编译期，类加载期织入等等，Spring实现AOP的方法则就是利用了动态代理机制，正因如此，才会导致某些情况下@Async和@Transactional不生效。 @Async注解使用如下 @EnableAsync //添加此注解开启异步调用（可用在配置类上，也可在启动类上标注） public
联合使用Spring的@Transactional和@Async注解的思考
baidu_38827679的博客
03-31 2437
一次使用Spring的@Transactional和@Async注解的思考
带有@Transactional和@Async的循环依赖问题
12-21
今天我们来探讨一个有意思的spring源码问题，也是一个学生告诉了我现象我从源码里面找到了这个有意思的问题。 首先我们看service层的代码案例，如下： @Service("transationServiceImpl") public class TransationServiceImpl implements TransationService { @Autowired TransationService transationService; @Transactional @Async @Override public void transa
Spring循环引用-@Async注解启动报错分析
liangbo7的博客
12-18 3996
Spring循环引用-@Async注解启动报错分析
添加@Async注解，导致spring启动失败
liangsheng_g的专栏
08-29 3499
文章目录前言一、异常表现，抛出内容1.1循环依赖的两个class1.2 启动报错二、原因分析2.1 主要原因2.2 循环依赖放入二级缓存处逻辑2.3 initializeBean生成的对象2.4 再次分析原因总结 前言 在这篇文章里，最后总结处，我说了会讲讲循环依赖中，其中一个类添加@Async有可能会导致注入失败而抛异常的情况，今天就分析一下。 一、异常表现，抛出内容 1.1循环依赖的两个class CycleService1 @Service public class CycleService1
@Async 导致该Bean在循环依赖时启动报错
weixin_37760377的博客
05-12 552
今天在开发代码的时候遇到了一个启动错误，错误内容大致就是： org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'classA': Bean with name 'classA' has been injected into other beans [classB] in its raw version as part of a circular referen
@Async注解和循环引用的启动容器报错问题
zlj1217的博客
07-18 457
现象及相关引用博客 https://segmentfault.com/a/1190000021217176 问题 Spring其实是可以帮助解决循环依赖的，但是在循环依赖的两个bean上有一个加入了@Async注解之后，在启动的时候就报错不能进行循环依赖。 @Component public class A { @Autowired private B b; @Async public void testA() { System.out.println(T
spring循环依赖下使用@Async注解导致报错问题
weixin_44771989的博客
06-15 641
spring的三级缓存和循环依赖
@Async注解引发的报错之组件导入
weixin_43810802的博客
02-02 975
引入 我有一个TaskService： @Service public class TaskServiceImpl implements TaskService { @Autowired private AlgorithmService algorithmService; @Autowired private RobotService robotService; @Override @Async public void getTaskExecut
由@Async引起的Spring循环引用
qq_42559485的博客
04-16 835
场景&原因 package com.shi.cycleref; import org.springframework.scheduling.annotation.Async; import org.springframework.scheduling.annotation.EnableAsync; import org.springframework.stereotype.Component; import javax.annotation.Resource; /** * @author s
Spring 使用@Async出现循环依赖Bean报错的解决方案
weixin_30425949的博客
06-30 713
初现端倪 Caused by:org.springframework.beans.factory.BeanCurrentlyInCreationException: Errorcreating bean with name 'asyncUpdate': Bean with name 'asyncUpdate' has beeninjected into other beans [dealerSer...
@Transactional导致的循环依赖问题BeanNotOfRequiredTypeException
于琦海
03-20 478
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'b': Unsatisfied dependency expressed through field 'a'; nested exception is org.springframework.beans.factory.BeanNotOfRequiredTypeException: Bean n
springCloud项目中加了service注解反而报错？？？（已解决）
awodwde的博客
02-11 795
在impl中加了serviece注解，启动服务时 org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'brandController': Injection of resource dependencies failed; nested exception is org.springframework.beans.factory.NoUniqueBeanDefinition..
在使用 Spring Boot 和 MyBatis 动态切换数据源时遇到的问题以及解决方法
热门推荐
啦啦啦啦 la
12-22 2万+
相关项目地址:https://github.com/helloworlde/SpringBoot-DynamicDataSource/tree/dev 1. org.apache.ibatis.binding.BindingException: Invalid bound statement (not found) 在使用了动态数据源后遇到了该问题，从错误信息来看是因为没有找到 *.xml 文件
SpringBoot-@Async-@EnableAsync-ApplicationContext与ApplicationListener搭配-ApplicationEvent创建响应式异步调用。
最新发布
qq_45568546的博客
04-19 288
重写类需要被@Bean注入（可以用@Component等价注解代替）。函数上添加@Async可以让这个函数使用类似单独线程资源独立执行从而不影响函数的主流程。使用ApplicationContext的实例函数publishEvent(ApplicationEvent)发布函数就可以唤醒ApplicationListener执行onApplicationEvent(Event)函数。ApplicationEvent是抽象类，是ApplicationListener接口的模板函数类型。
@Async注解引发的报错之解决
weixin_43810802的博客
05-15 985
solution问题解决 问题解决 在上篇文章中，我们知道了TaskServiceImpl在注入RobotServiceImpl前后从raw version变成了代理。而且我们希望找到dependentBeanMap这个map维护的地方。 在属性注入的代码里，我们看到了dependentBeanMap维护的地方。那么我们想：能不能不进这个方法？ ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值