spring boot 全局异常处理无法直接捕获依赖注入(di)失败,因为 di 发生在 bean 创建阶段,早于 dispatcherservlet 的异常处理流程。要解决此问题,需实现 applicationcontextinitializer 接口并在 spring.factories 中注册,在容器刷新前拦截 beancreationexception 并返回自定义错误响应。

为什么 @ControllerAdvice 抓不到 DI 异常
@ControllerAdvice 仅作用于请求处理阶段,而 DI 异常发生在应用启动或懒加载 Bean 首次访问时,此时尚未进入 Web 请求上下文。因此,必须使用更底层的机制来捕获容器初始化阶段的错误。

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
@SpringBootApplication
public class Application {
public static void main(String[] args) {
SpringApplication.run(Application.class, args);
}
}

import org.springframework.context.ApplicationContextInitializer;
import org.springframework.context.ConfigurableApplicationContext;
import org.springframework.core.Ordered;
import org.springframework.core.annotation.Order;
import org.springframework.boot.context.event.ApplicationFailedEvent;
import org.springframework.boot.diagnostics.AbstractFailureAnalyzer;
import org.springframework.boot.diagnostics.FailureAnalyzer;
import org.springframework.beans.factory.BeanCreationException;
import java.util.Optional;
@Order(Ordered.HIGHEST_PRECEDENCE)
public class DiFailureAnalyzer extends AbstractFailureAnalyzer<BeanCreationException> {
@Override
protected FailureAnalysis analyze(Throwable failure, BeanCreationException exception) {
return new FailureAnalysis(
"Dependency Injection Failed: " + exception.getMessage(),
"Check your @Autowired fields and bean definitions.",
exception
);
}
}
public class DiInitializer implements ApplicationContextInitializer<ConfigurableApplicationContext> {
@Override
public void initialize(ConfigurableApplicationContext context) {
context.addApplicationListener(event -> {
if (event instanceof ApplicationFailedEvent) {
Optional.ofNullable(((ApplicationFailedEvent) event).getFailure())
.filter(BeanCreationException.class::isInstance)
.ifPresent(ex -> System.err.println("DI Error Caught: " + ex.getMessage()));
}
});
}
}
如何配置自定义失败分析器
通过继承 AbstractFailureAnalyzer 并重写 analyze 方法,可以拦截特定的异常类型。将此类注册为 Spring 组件后,它会在应用启动失败时自动执行,从而提供清晰的错误信息而非默认的堆栈跟踪。


















