奇怪的是在我Ubuntu的机器上打包到测试服务器上报错，而从另外一台windows机器打包时就没问题，刚开始还以为是maven和jdk的问题。报错的启动时日志如下：
2019-06-14 14:03:45,644 org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter [main] (LoggingFailureAnalysisReporter.java:38) DEBUG --> Application failed to start due to an exception
org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name ‘heliPayChannelAsynService‘: Bean with name ‘heliPayChannelAsynService‘ has been injected into other beans [heliPayChannelService] 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 ‘getBeanNamesOfType‘ with the ‘allowEagerInit‘ flag turned off, for example.
Description:
The dependencies of some of the beans in the application context form a cycle:
| operManagerServiceImpl (field private com.ps.ydxjd.core.api.service.order.impl.OrderServiceImpl com.ps.ydxjd.core.api.service.manager.impl.OperManagerServiceImpl.orderServiceImpl)
↑ ↓
| orderServiceImpl (field private com.ps.ydxjd.core.api.service.pay.IPayService com.ps.ydxjd.core.api.service.order.impl.OrderServiceImpl.payService)
↑ ↓
| payService (field private com.ps.ydxjd.core.api.service.pay.HeliPayChannelAsynService com.ps.ydxjd.core.api.service.pay.impl.PayServiceImpl.heliPayChannelAsynService)
↑ ↓
| heliPayChannelAsynService
查到文章也有类似的经历，
heliPayChannelAsynService加上了@EnableAsync(proxyTargetClass = true)，方法上用了@Async
https://stackoverflow.com/questions/27400759/spring-3-2-project-fails-to-load-when-enableasync-is-added-to-configuration
https://stackoverflow.com/questions/28985144/spring-autowired-aop-circular-dependency
大概的意思是注入方法用了@Async的对象早于AOP创建proxy类，当spring初始化applicationContext后，发现注入的对象并不是proxy类。于是报错
解决方法是在注入heliPayChannelAsynService的地方加上 @Lazy(value = true)
原文地址：https://www.cnblogs.com/zjhgx/p/11047811.html