You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@dubbo.apache.org by GitBox <gi...@apache.org> on 2021/07/24 14:29:09 UTC

[GitHub] [dubbo] zhwq1216 opened a new issue #8347: DubboConfigEarlyInitializationPostProcessor cause PostProcessorRegistrationDelegate$BeanPostProcessorChecker log 'not eligible for getting processed by all BeanPostProcessors'

zhwq1216 opened a new issue #8347:
URL: https://github.com/apache/dubbo/issues/8347


   - [ ] I have searched the [issues](https://github.com/apache/dubbo/issues) of this repository and believe that this is not a duplicate.
   - [ ] I have checked the [FAQ](https://github.com/apache/dubbo/blob/master/FAQ.md) of this repository and believe that this is not a duplicate.
   
   ### Environment
   
   * Dubbo version: 2.7.12
   * Operating System version: centos7.4
   * Java version: jdk1.8
   
   ### Steps to reproduce this issue
   Set the  org.springframework log level to INFO, then there many logs such as:
   ```INFO  org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'xxx' of type [xxx.xxx.xxx] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)```
   
   Tracking the ```org.springframework.context.support.PostProcessorRegistrationDelegate#registerBeanPostProcessors``` method, it is found that the postProcessorNames contains the instance of DubboConfigEarlyInitializationPostProcessor, and because ```DubboBeanConfigEarlyInitializationPostProcessor#initBeanFactory``` has been added to self to the beanPostProcessors list. Due to this BeanPostProcessor duplication, the beanProcessorTargetCount will be one more than the final beanPostProcessors list. Therefore, the above INFO log information is printed in ```org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker```.
   ```
   		String[] postProcessorNames = beanFactory.getBeanNamesForType(BeanPostProcessor.class, true, false);
   
   		// Register BeanPostProcessorChecker that logs an info message when
   		// a bean is created during BeanPostProcessor instantiation, i.e. when
   		// a bean is not eligible for getting processed by all BeanPostProcessors.
   		int beanProcessorTargetCount = beanFactory.getBeanPostProcessorCount() + 1 + postProcessorNames.length;
   		beanFactory.addBeanPostProcessor(new BeanPostProcessorChecker(beanFactory, beanProcessorTargetCount));
   ```
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org


[GitHub] [dubbo] CrazyHZM commented on issue #8347: DubboConfigEarlyInitializationPostProcessor cause PostProcessorRegistrationDelegate$BeanPostProcessorChecker log 'not eligible for getting processed by all BeanPostProcessors'

Posted by GitBox <gi...@apache.org>.
CrazyHZM commented on issue #8347:
URL: https://github.com/apache/dubbo/issues/8347#issuecomment-996448020


   fixed with #9397


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org


[GitHub] [dubbo] CrazyHZM closed issue #8347: DubboConfigEarlyInitializationPostProcessor cause PostProcessorRegistrationDelegate$BeanPostProcessorChecker log 'not eligible for getting processed by all BeanPostProcessors'

Posted by GitBox <gi...@apache.org>.
CrazyHZM closed issue #8347:
URL: https://github.com/apache/dubbo/issues/8347


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org


[GitHub] [dubbo] tcsp commented on issue #8347: DubboConfigEarlyInitializationPostProcessor cause PostProcessorRegistrationDelegate$BeanPostProcessorChecker log 'not eligible for getting processed by all BeanPostProcessors'

Posted by GitBox <gi...@apache.org>.
tcsp commented on issue #8347:
URL: https://github.com/apache/dubbo/issues/8347#issuecomment-922243848


   i have the same problem, then how to fix it?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org