Overriding bean definition for bean 'X': replacing [Generic bean Y]

Question

I have the configuration like below:

batch:job id="reconciliationJob" job-repository="jobRepository" restartable="true"

and during application context startup I receive something like this in the log:

[INFO] [] [] Overriding bean definition for bean 'reconciliationJob': replacing [Generic bean: class [org.springframework.batch.core.configuration.xml.SimpleFlowFactoryBean]; scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null] with [Generic bean: class [org.springframework.batch.core.configuration.xml.JobParserJobFactoryBean]; scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null]

How can I solve this overriding problem?

is there a way to get rid of these log messages? – OhadR Oct 21 '15 at 15:21 — OhadR, Oct 21 '15 at 15:21

score 7 · Answer 1 · edited Jul 05 '21 at 08:44

7

I got the same error. My problem was that I marked the class with @Service then in one of the @Configuration classes I created a @Bean out of it with the same name as the class.

edited Jul 05 '21 at 08:44

ScanQR

3,740
1
13
30

answered Mar 10 '16 at 19:14

Lakatos Gyula

3,949
7
35
56

Babken Vardanyan · Answer 2 · 2016-02-08T09:24:24.973

4

This happens when Spring parses the same applicationContext.xml twice.

This can happen when for example your have duplicate/overriding <context-param> imports in your WEB.xml.

To solve the issue leave only the root applicationContext.xml there and remove the children.

edited Feb 08 '16 at 09:24

answered Feb 08 '16 at 07:30

Babken Vardanyan

14,090
13
68
87

score 3 · Answer 3 · answered Sep 26 '13 at 08:00

3

This is not an error, is only an [INFO] and is a substitution done by Spring; you can see something similar about "step" scoped beans.
For example, if you have a bean marked as

<bean id="myBean" class="path.to.beanClass" scope="step" />

this will be replaced by a bean with name scopedTarget.myBean.
Lookup at StepScope doc and source

answered Sep 26 '13 at 08:00

Luca Basso Ricci

17,829
2
47
69

1

Due to this duplicate bean definition, server wont start properly for few cases. It leads to bean creation exception - **Requested bean is currently in creation: Is there an unresolvable circular reference?** Reference : http://stackoverflow.com/questions/10008714/requested-bean-is-currently-in-creation-is-there-an-unresolvable-circular-refer Two reasons for this: 1. Circular dependency 2. Duplicate bean definition FYI @przodownikPracy – Paramesh Korrakuti Feb 20 '15 at 10:17

score 1 · Answer 4 · answered Dec 02 '18 at 09:45

1

I experienced something similar and I just changed the name of the class and it worked. Still can't figure out why. I'll update if I understand it better.

But start with changing the bean's class name.

answered Dec 02 '18 at 09:45

Avi

21,182
26
82
121

score -2 · Answer 5 · edited Nov 05 '17 at 08:21

-2

I had a similar problem and I resolved it using dependency:analyze in run maven -> goals. I found unused dependencies in my pom and I removed the unused dependencies.

Note: take care when removing the dependencies because the result of dependency:analyze it is not secure .

edited Nov 05 '17 at 08:21

Mark Rotteveel

100,966
191
140
197

answered Nov 05 '17 at 04:36

carloss vasquez casas

11
1

Overriding bean definition for bean 'X': replacing [Generic bean Y]

5 Answers5