​

异常分析

异常信息

is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

异常触发

int beanProcessorTargetCount = beanFactory.getBeanPostProcessorCount() + 1 + postProcessorNames.length;beanFactory.addBeanPostProcessor(new BeanPostProcessorChecker(beanFactory, beanProcessorTargetCount));

异常触发条件

@Override
public Object postProcessAfterInitialization(Object bean, String beanName) {if (bean != null && !(bean instanceof BeanPostProcessor) && !isInfrastructureBean(beanName) &&this.beanFactory.getBeanPostProcessorCount() < this.beanPostProcessorTargetCount) {if (logger.isInfoEnabled()) {logger.info("Bean '" + beanName + "' of type [" + bean.getClass().getName() +"] is not eligible for getting processed by all BeanPostProcessors " +"(for example: not eligible for auto-proxying)");}}return bean;
}

异常触发方法

org.springframework.context.support.PostProcessorRegistrationDelegate.BeanPostProcessorChecker#postProcessAfterInitialization

总结：

1. bean不为BeanPostProcessor

异常出现场景

项目启动

总结

业务bean在BPP实例化前被实例化了。理想情况下应该让spring先实例化所有的BPP后，再实例化我们的业务bean，这样业务bean才能被所有BPP处理，如果有业务bean先于任何BPP实例化，那么这个业务bean就不会被还未实例化的BPP处理了，这个就是日志提示的原因。