Closed ldcsaa closed 11 months ago
4.3.0
@huayanYu 升级到 4.3.0 后,问题还是存在~~
2024-01-04 14:27:31.958 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'io.github.hpsocket.soa.starter.data.mysql.config.SoaGlobalTransactionConfig' of type [io.github.hpsocket.soa.starter.data.mysql.config.SoaGlobalTransactionConfig] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.133 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'io.github.hpsocket.soa.starter.data.mysql.config.SoaDataSourceConfig' of type [io.github.hpsocket.soa.starter.data.mysql.config.SoaDataSourceConfig] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.151 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'org.springframework.cloud.commons.config.CommonsConfigAutoConfiguration' of type [org.springframework.cloud.commons.config.CommonsConfigAutoConfiguration] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.158 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'org.springframework.cloud.client.loadbalancer.LoadBalancerDefaultMappingsProviderAutoConfiguration' of type [org.springframework.cloud.client.loadbalancer.LoadBalancerDefaultMappingsProviderAutoConfiguration] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.163 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'loadBalancerClientsDefaultsMappingsProvider' of type [org.springframework.cloud.client.loadbalancer.LoadBalancerDefaultMappingsProviderAutoConfiguration$$Lambda$1106/0x00000008014fdc70] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.174 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'defaultsBindHandlerAdvisor' of type [org.springframework.cloud.commons.config.DefaultsBindHandlerAdvisor] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.216 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceAssistConfiguration' of type [com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceAssistConfiguration$$SpringCGLIB$$0] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.229 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceCreatorAutoConfiguration$HikariDataSourceCreatorConfiguration' of type [com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceCreatorAutoConfiguration$HikariDataSourceCreatorConfiguration$$SpringCGLIB$$0] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.237 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'hikariDataSourceCreator' of type [com.baomidou.dynamic.datasource.creator.hikaricp.HikariDataSourceCreator] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.243 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceCreatorAutoConfiguration$DruidDataSourceCreatorConfiguration' of type [com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceCreatorAutoConfiguration$DruidDataSourceCreatorConfiguration$$SpringCGLIB$$0] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.260 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'druidDataSourceCreator' of type [com.baomidou.dynamic.datasource.creator.druid.DruidDataSourceCreator] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.265 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceCreatorAutoConfiguration' of type [com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceCreatorAutoConfiguration$$SpringCGLIB$$0] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.274 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'basicDataSourceCreator' of type [com.baomidou.dynamic.datasource.creator.basic.BasicDataSourceCreator] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.277 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'jndiDataSourceCreator' of type [com.baomidou.dynamic.datasource.creator.jndi.JndiDataSourceCreator] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.287 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'dataSourceInitEvent' of type [com.baomidou.dynamic.datasource.event.EncDataSourceInitEvent] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.292 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'dataSourceCreator' of type [com.baomidou.dynamic.datasource.creator.DefaultDataSourceCreator] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.299 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'ymlDynamicDataSourceProvider' of type [com.baomidou.dynamic.datasource.provider.YmlDynamicDataSourceProvider] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.642 INFO [main] c.a.d.pool.DruidDataSource#init(L:1007) -> {dataSource-1,master} inited
2024-01-04 14:27:32.679 INFO [main] c.a.d.pool.DruidDataSource#init(L:1007) -> {dataSource-2,slave_01} inited
2024-01-04 14:27:32.714 INFO [main] c.a.d.pool.DruidDataSource#init(L:1007) -> {dataSource-3,slave_02} inited
2024-01-04 14:27:32.716 INFO [main] c.b.d.datasource.DynamicRoutingDataSource#addDataSource(L:158) -> dynamic-datasource - add a datasource named [slave_01] success
2024-01-04 14:27:32.716 INFO [main] c.b.d.datasource.DynamicRoutingDataSource#addDataSource(L:158) -> dynamic-datasource - add a datasource named [slave_02] success
2024-01-04 14:27:32.716 INFO [main] c.b.d.datasource.DynamicRoutingDataSource#addDataSource(L:158) -> dynamic-datasource - add a datasource named [master] success
2024-01-04 14:27:32.716 INFO [main] c.b.d.datasource.DynamicRoutingDataSource#afterPropertiesSet(L:241) -> dynamic-datasource initial loaded [3] datasource,primary datasource named [master]
2024-01-04 14:27:32.716 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'dynamicRoutingDataSource' of type [com.baomidou.dynamic.datasource.DynamicRoutingDataSource] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.743 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'dynamicRoutingTransactionManager' of type [org.springframework.jdbc.support.JdbcTransactionManager] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.779 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'soaTransactionAttributeSourceNameMapProvider' of type [io.github.hpsocket.soa.starter.data.mysql.config.SoaGlobalTransactionConfig$1] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.789 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'requiredRuleBasedTransactionAttribute' of type [org.springframework.transaction.interceptor.RuleBasedTransactionAttribute] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.805 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'readOnlyRuleBasedTransactionAttribute' of type [org.springframework.transaction.interceptor.RuleBasedTransactionAttribute] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.810 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'dynamicRoutingTransactionAdvice' of type [org.springframework.transaction.interceptor.TransactionInterceptor] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.811 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'dynamicRoutingTransactionAdvisor' of type [org.springframework.aop.support.DefaultPointcutAdvisor] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-01-04 14:27:32.812 WARN [main] o.s.c.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker#postProcessAfterInitialization(L:437) -> Bean 'com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceAopConfiguration' of type [com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceAopConfiguration] 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 [meterRegistryPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.
meterRegistryPostProcessor ??
@SpringBootApplication(exclude = SpringDataWebAutoConfiguration.class) 试试
Enviroment
JDK Version(required): 17
SpringBoot Version(required): 3.2.1
dynamic-datasource-spring-boot-starter Version(required): 4.2.0
druid Version(optional): 1.2.20
Describe what happened
升级到spring-boot 3.2.x 后,应用程序启动时会打印警告以下信息。
感觉与dynamic-datasource有关,麻烦排查一下。
(注:spring-boot 3.1.x 也有这些警告信息,但它的日志级别是INFO,所以没有留意。)
不出现警告。
出现警告。
Steps to reproduce