Spring中如何避免错误配置属性刷新引发的Bean初始化异常

我有一个Spring Boot应用，其中包含多个无需重启应用即可刷新的配置类，示例如下：

@Setter
@Getter
@Component
@RefreshScope
@ConfigurationProperties(prefix = "test")
class TestConfigProps {

    private Integer val;
}

正常情况下Bean刷新工作正常，但当配置刷新和Bean重新初始化过程中出现异常时（例如将字符串而非整数传入test.value），会因@RefreshScope的代理特性触发无限的Bean初始化异常：

Error querying consul Key/Values for context 'App/'. Message: Error creating bean with name 'testConfigProps' nested exception is org.springframework.boot.context.properties.bind.BindException: Failed to bind properties under 'test.value' to Integer 

Spring在刷新事件中会先销毁旧Bean再创建新Bean，相关逻辑如下：

public void refreshAll() {
    super.destroy();
    this.context.publishEvent(new RefreshScopeRefreshedEvent());
}

请问如何仅在新属性验证通过时创建刷新后的Bean，验证失败则保留原有Bean？

1. 自定义RefreshScope实现预校验逻辑 #

继承默认的RefreshScope，重写refreshAll方法，在销毁旧Bean前先尝试加载并验证新配置，仅在验证通过时执行刷新：

@Component
@Primary
public class SafeRefreshScope extends RefreshScope {

    private final Environment environment;
    private static final Logger log = LoggerFactory.getLogger(SafeRefreshScope.class);

    public SafeRefreshScope(Environment environment) {
        this.environment = environment;
    }

    @Override
    public void refreshAll() {
        boolean validationPassed = true;
        // 遍历所有@RefreshScope下的配置类，验证新配置合法性
        for (String beanName : getContext().getBeanDefinitionNames()) {
            BeanDefinition definition = getContext().getBeanDefinition(beanName);
            if (definition.getScope().equals("refresh")) {
                try {
                    // 实例化临时Bean并绑定新配置，验证格式
                    Object tempBean = getContext().getBeanFactory().createBean(definition.getBeanClassName());
                    ConfigurationPropertiesBinder binder = new ConfigurationPropertiesBinder(environment);
                    binder.bind(tempBean);
                } catch (Exception e) {
                    validationPassed = false;
                    log.error("配置验证失败：Bean {} 无法绑定新属性", beanName, e);
                }
            }
        }

        if (validationPassed) {
            super.destroy();
            this.context.publishEvent(new RefreshScopeRefreshedEvent());
            log.info("配置验证通过，已刷新所有Bean");
        } else {
            log.warn("配置验证未通过，保留原有Bean实例");
        }
    }
}

2. 为配置类添加前置校验逻辑 #

结合JSR-380校验注解和自定义刷新拦截器，在触发刷新前完成配置合法性校验：
首先给配置类添加校验注解：

@Setter
@Getter
@Component
@RefreshScope
@ConfigurationProperties(prefix = "test")
@Validated
class TestConfigProps {

    @NotNull
    private Integer val;
}

然后自定义Actuator刷新端点的处理器，替换默认的刷新逻辑：

@Component
@Endpoint(id = "safe-refresh")
public class SafeRefreshEndpoint {

    private final SafeRefreshScope safeRefreshScope;

    public SafeRefreshEndpoint(SafeRefreshScope safeRefreshScope) {
        this.safeRefreshScope = safeRefreshScope;
    }

    @WriteOperation
    public Map<String, String> safeRefresh() {
        safeRefreshScope.refreshAll();
        return Collections.singletonMap("status", "refresh completed (if validation passed)");
    }
}

3. 基于代理的回退机制 #

通过自定义BeanPostProcessor为@RefreshScopeBean添加代理，当新Bean初始化失败时自动回退到旧实例：

@Component
public class RefreshFallbackProcessor implements BeanPostProcessor, ApplicationContextAware {

    private ApplicationContext context;
    private final Map<String, Object> beanSnapshots = new ConcurrentHashMap<>();
    private static final Logger log = LoggerFactory.getLogger(RefreshFallbackProcessor.class);

    @Override
    public void setApplicationContext(ApplicationContext applicationContext) throws BeansException {
        this.context = applicationContext;
    }

    @Override
    public Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException {
        if (AnnotationUtils.findAnnotation(bean.getClass(), RefreshScope.class) != null) {
            beanSnapshots.put(beanName, bean);
            // 创建动态代理
            return Proxy.newProxyInstance(
                    bean.getClass().getClassLoader(),
                    bean.getClass().getInterfaces(),
                    (proxy, method, args) -> {
                        try {
                            Object currentBean = context.getBean(beanName);
                            return method.invoke(currentBean, args);
                        } catch (Exception e) {
                            log.error("获取刷新后Bean失败，回退到旧实例：{}", beanName, e);
                            return method.invoke(beanSnapshots.get(beanName), args);
                        }
                    }
            );
        }
        return bean;
    }
}

4. 配置中心层面的前置校验 #

如果使用Consul等配置中心，可在配置推送阶段添加校验逻辑：

• 在CI/CD流程中加入配置格式校验步骤，确保只有符合类型要求的配置才能被提交到配置中心
• 利用Consul的KV存储钩子，在配置写入时触发校验脚本，拦截非法配置

内容的提问来源于stack exchange，提问作者strelchm