My Oracle Support Banner

Spring Application Deployment Failed with NoSuchBeanDefinitionException and Error Creating Bean (Doc ID 2397321.1)

Last updated on OCTOBER 08, 2018

Applies to:

Oracle WebLogic Server - Version and later
Information in this document applies to any platform.


 On WLS, the following exceptions is seen during Spring application deployment:

Error 1 -

<BEA-000000> <Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'MyWeldBean' defined in URL [jar:file:/web/bea/oltd139/Middleware/oracle_common/modules/thirdparty/ .jbatch.container-1.0.1.jar!/com/ibm/jbatch/container/services/impl/WeldSEBatchArtifactFactoryImpl.class]

Error 2 -

<Mar 6, 2018 12:22:49,998 PM EST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application "XXXWebService_spring4". weblogic.application.ModuleException: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'weblogic.messaging.saf.internal.SAFServerService' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@javax.inject.Inject(), @javax.inject.Named(value=SAFServerService)} at weblogic.application.internal.ExtensibleModuleWrapper.start( at weblogic.application.internal.flow.ModuleListenerInvoker.start( at weblogic.application.internal.flow.ModuleStateDriver$ at weblogic.application.internal.flow.ModuleStateDriver$ at weblogic.application.utils.StateMachineDriver.nextState( Truncated. see log file for complete stacktrace Caused By: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.