- Notifications
You must be signed in to change notification settings - Fork 38.8k
Closed
Labels
in: dataIssues in data modules (jdbc, orm, oxm, tx)Issues in data modules (jdbc, orm, oxm, tx)type: regressionA bug that is also a regressionA bug that is also a regression
Milestone
Description
I'm not sure if this is the right place to log this issue, but thought I would start here.
When @EnableRetry is added to a Boot application also using spring-boot-actuator, the following occurs:
trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.retry.annotation.RetryConfiguration' of type [org.springframework.retry.annotation.RetryConfiguration$$EnhancerBySpringCGLIB$$2cf7388d] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) The same is also true when adding spring-boot-starter-jdbc along with spring-boot-actuator.
trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) It appears that the MeterRegistryPostProcessor is causing some Advisors and other beans to be initialized early.
This initializr generated application shows the ProxyTransactionmanagementConfiguration message during startup.
Adding @EnableRetry and the following will cause the RetryConfiguration message during startup.
<dependency> <groupId>org.springframework.retry</groupId> <artifactId>spring-retry</artifactId> </dependency> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-aspects</artifactId> </dependency> Metadata
Metadata
Assignees
Labels
in: dataIssues in data modules (jdbc, orm, oxm, tx)Issues in data modules (jdbc, orm, oxm, tx)type: regressionA bug that is also a regressionA bug that is also a regression