Ali Aliyev
Ali Aliyev

Reputation: 1

Spring Boot Warn, when launching service - "Bean'org.springframework.cloud.client.loadbalancer.LoadBalancerAutoConfiguration'"

After migrating Spring Boot version from 2.7.14 to 3.2.2 I get a warning when I start the service.

WARN [info-service,,]" 50964 --- [main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.client.loadbalancer.LoadBalancerAutoConfiguration' of type [org.springframework.cloud.client.loadbalancer.LoadBalancerAutoConfiguration] 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 [lbRestClientPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.

OR

" WARN [info-service,,]" 50964 --- [main] trationDelegate$BeanPostProcessorChecker : Bean 'default.org.springframework.cloud.loadbalancer.config.LoadBalancerAutoConfiguration.LoadBalancerClientSpecification' of type [org.springframework.cloud.loadbalancer.annotation.LoadBalancerClientSpecification] 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 [lbRestClientPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.

Before migrate version everything worked properly. I tried to find documentation or way to solve this issue but could not.

Upvotes: 0

Views: 820

Answers (1)

Henning
Henning

Reputation: 3899

The warnings are produced by the auto-configuration code of Spring Cloud Load Balancer. As of now, it will be resolved with the next release of Spring Cloud: https://github.com/spring-cloud/spring-cloud-commons/pull/1361

The warnings do not indicate an actual issue in this particular case.

Until the fix is released, you can silence any such warning by setting the log level of the logger for org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker to ERROR such that it doesn't log warnings. This comes at the price that you don't see any such warning, which may disable warnings for other configurations that you might want to see.

Upvotes: 0

Related Questions