Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BeanPostProcessorChecker waring #152

Open
luna825 opened this issue May 2, 2024 · 0 comments
Open

BeanPostProcessorChecker waring #152

luna825 opened this issue May 2, 2024 · 0 comments

Comments

@luna825
Copy link

luna825 commented May 2, 2024

spring boot 3.2 + java17, 项目中有自己实现的BeanPostProcessor,出现以下警告

2024-05-01 23:39:08.804  WARN 32473 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'com.mzt.logapi.starter.configuration.LogRecordProxyAutoConfiguration' of type [com.mzt.logapi.starter.configuration.LogRecordProxyAutoConfiguration$$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 [permissionMetaCollector]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-05-01 23:39:08.809  WARN 32473 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'mzt.log.record-com.mzt.logapi.starter.configuration.LogRecordProperties' of type [com.mzt.logapi.starter.configuration.LogRecordProperties] 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 [permissionMetaCollector]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2024-05-01 23:39:08.812  WARN 32473 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'logRecordPerformanceMonitor' of type [com.mzt.logapi.service.impl.DefaultLogRecordPerformanceMonitor] 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 [permissionMetaCollector]? Check the corresponding BeanPostProcessor declaration and its dependencies.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant