WARN BeanPostProcessorChecker:Bean 'x' of type [y] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [projectingArgumentResolverBeanPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.

[billschen]

I upgrade my code to spring-boot 3.2.0
dependencies:
starter-data-jdbc,starter-data-jpa,starter-data-redis,starter-jdbc,starter-security,starter-web....
when use gradle bootRun command ,out put so many WARN mesage like:

2023-11-27T15:40:01.396+08:00 WARN 20020 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'liaisonInCustomerRoleService' of type [com.gdtech.oadingtalk.service.contractmanager.fundamentals.LiaisonInCustomerRoleService] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [projectingArgumentResolverBeanPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2023-11-27T15:40:01.430+08:00 WARN 20020 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'customerRoledLiaisonRepository' of type [jdk.proxy2.$Proxy1478] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [projectingArgumentResolverBeanPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.

2023-11-27T15:56:28.592+08:00 WARN 23981 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'jpa.named-queries#2280' of type [org.springframework.data.repository.core.support.PropertiesBasedNamedQueries] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [projectingArgumentResolverBeanPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.

almost every calss annotation with Service or Repoistory ouput WARN message like above.

I don't define a BeanPostProcessor name ProjectingArgumentResolverBeanPostProcessor in my code.
those WARN message seriously slowing down the startup speed.
Are there any suggestions about how best to tackle the problem? thanks a lot!

[mp911de]

From which version are you upgrading? The configuration class and ProjectingArgumentResolverBeanPostProcessor haven't been changed in the past couple of years.

Leaving the link to spring-projects/spring-boot#38558 here.

[billschen]

I update my code many times ,my be 2.1

[shivtrpm]

I have the same problem too. Almost all of the beans are getting warnings after upgrading to spring boot 3.2

[shivtrpm]

need help asap, before we roll it out to prod by end of this week.

[underbell]

I have the same problem too. my before version is 3.1.5

spring-projects/spring-batch#4489

[billschen]

my be the problem is the deprecated springframework.security annotation like EnableGlobalMethodSecurity or GlobalMethodSecurityConfiguration .
I comment the code and WARN message gone!

[mp911de]

@billschen can you continue the discussion please on the Boot ticket? Spring Data doesn't seem to be the right place.

[wilkinsona]

@shivtrpm If you need help then you have to make it as easy as you can for people to provide that help. The best way to do so is by creating a minimal, reproducible example and sharing it with us. You can do so by adding a link to it on the Spring Boot issue.

[gbvbahia01]

on version 3.1.7 there is no warns, but after upgrade to 3.2.1 there are some.
In my case indicating the bean jobRegistryBeanPostProcessor as root cause.