Warnings "Bean is not eligible..." with Spring Boot

26 views
Skip to first unread message

Ivo Maixner

unread,
Oct 4, 2024, 6:16:36 AM10/4/24
to javamelody
Hi,
thanks a lot for Java Melody. I just plugged it in into a Spring Boot app and it all works.

There are some warnings during the start of the app, though, which I can't find a way of getting rid of:

...trationDelegate$BeanPostProcessorChecker : Bean 'net.bull.javamelody.JavaMelodyAutoConfiguration' of type [net.bull.javamelody.JavaMelodyAutoConfiguration$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). The currently created BeanPostProcessor [monitoringDataSourceBeanPostProcessor] is declared through a non-static factory method on that class; consider declaring it as static instead.

...trationDelegate$BeanPostProcessorChecker : Bean 'monitoringSpringAdvisor' of type [net.bull.javamelody.MonitoringSpringAdvisor] 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 [healthEndpointGroupsBeanPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.

...trationDelegate$BeanPostProcessorChecker : Bean 'monitoringSpringServiceAdvisor' of type [net.bull.javamelody.MonitoringSpringAdvisor] 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 [healthEndpointGroupsBeanPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.

and four more like the above.

Spring Boot v 3.3.2
javamelody-spring-boot-starter v. 2.2.0

Any advice, suggestions?

Thank you,
Ivo

evernat

unread,
Feb 21, 2025, 11:51:27 AMFeb 21
to javamelody
Hello,
This is fixed for the next release (2.6.0) : https://github.com/javamelody/javamelody/commit/a5f5f6b
bye,
Emeric
Reply all
Reply to author
Forward
0 new messages