Spring Boot启动报错 :ApplicationEventMulticaster not initialized - call 'refresh'

蔚落 2022-05-25 09:29 201阅读 0赞

**一、问题描述**

Spring-boot项目一启动就报错:

java.lang.IllegalStateException: ApplicationEventMulticaster not initialized - call 'refresh' before multicasting events via the context: org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@10617a1: startup date [Fri May 11 19:04:42 CST 2018]; root of context hierarchy
    	at org.springframework.context.support.AbstractApplicationContext.getApplicationEventMulticaster(AbstractApplicationContext.java:414)
    	at org.springframework.context.support.ApplicationListenerDetector.postProcessBeforeDestruction(ApplicationListenerDetector.java:97)
    	at org.springframework.beans.factory.support.DisposableBeanAdapter.destroy(DisposableBeanAdapter.java:253)
    	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroyBean(DefaultSingletonBeanRegistry.java:578)
    	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingleton(DefaultSingletonBeanRegistry.java:554)
    	at org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingleton(DefaultListableBeanFactory.java:961)
    	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingletons(DefaultSingletonBeanRegistry.java:523)
    	at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.destroySingletons(FactoryBeanRegistrySupport.java:230)
    	at org.springframework.beans.factory.support.DefaultListableBeanFactory.destroySingletons(DefaultListableBeanFactory.java:968)
    	at org.springframework.context.support.AbstractApplicationContext.destroyBeans(AbstractApplicationContext.java:1030)
    	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:556)
    	at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:122)
    	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693)
    	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360)
    	at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
    	at com.xxxx.app.taobo.TaobaoApplication.main(TaobaoApplication.java:22)
    	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)
    2018-05-11 19:04:42.921-|-ERROR-|-restartedMain-|-org.springframework.boot.SpringApplication[771]-|-Application startup failed
    org.springframework.beans.factory.BeanDefinitionStoreException: Failed to parse configuration class [com.xxxx.app.taobo.TaobaoApplication]; nested exception is org.springframework.context.annotation.ConflictingBeanDefinitionException: Annotation-specified bean name 'loggingServiceImpl' for bean class [com.xxxx.cloud.service.logging.impl.LoggingServiceImpl] conflicts with existing, non-compatible bean definition of same name and class [com.xxxx.app.taobo.service.impl.LoggingServiceImpl]
    	at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:181)
    	at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:308)
    	at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:228)
    	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:270)
    	at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:93)
    	at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:687)
    	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:525)
    	at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:122)
    	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693)
    	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360)
    	at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
    	at com.xxxx.app.taobo.TaobaoApplication.main(TaobaoApplication.java:22)
    	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: org.springframework.context.annotation.ConflictingBeanDefinitionException: Annotation-specified bean name 'loggingServiceImpl' for bean class [com.xxxx.cloud.service.logging.impl.LoggingServiceImpl] conflicts with existing, non-compatible bean definition of same name and class [com.xxxx.app.taobo.service.impl.LoggingServiceImpl]
    	at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.checkCandidate(ClassPathBeanDefinitionScanner.java:345)
    	at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:283)
    	at org.springframework.context.annotation.ComponentScanAnnotationParser.parse(ComponentScanAnnotationParser.java:135)
    	at org.springframework.context.annotation.ConfigurationClassParser.doProcessConfigurationClass(ConfigurationClassParser.java:287)
    	at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:245)
    	at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:198)
    	at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:167)
    	... 16 common frames omitted
    Disconnected from the target VM, address: '127.0.0.1:55386', transport: 'socket'

**二、解决方法**

问题就出在:

Caused by: org.springframework.context.annotation.ConflictingBeanDefinitionException: Annotation-specified bean name 'loggingServiceImpl' for bean class [com.xxxx.cloud.service.logging.impl.LoggingServiceImpl] conflicts with existing

纯在冲突。进入与现有冲突，该类如下:

@Service
    public class LoggingServiceImpl implements LoggingService {
    
        @Override
        public void logPrint(String logStr) {
    
        }
    }

后来一想，好像引入的jar包也有这个类，而且是通过@Service注入进来的。。将文件重命名就行了。

Spring Boot启动报错 :ApplicationEventMulticaster not initialized - call 'refresh'

发表评论取消回复

还没有评论，来说两句吧...

相关阅读

相关 ApplicationEventMulticaster not initialized - call 'refresh' before multicasting events via the cont

相关 ActiveMQ启动报错：java.lang.IllegalStateException: BeanFactory not initialized or already closed - call ‘

相关 java.lang.IllegalStateException: BeanFactory not initialized or already closed - call ‘refresh‘ befo

相关 SSH框架整合出现“LifecycleProcessor not initialized - call 'refresh' before invoking”问题

相关 ActiveMQ启动报错:java.lang.IllegalStateException: LifecycleProcessor not initialized - call 'refresh' be

相关 Spring Boot启动报错 :ApplicationEventMulticaster not initialized - call 'refresh'

相关 BeanFactory not initialized or already closed - call 'refresh' before accessing beans解决

相关 LifecycleProcessor not initialized - call 'refresh' before invoking lifecycle methods via the contex

相关解决ApplicationEventMulticaster not initialized - call ‘refresh‘ before multicasting events异常

相关 spring boot项目启动报错