如何排查CompletionStage抛出的模糊空指针异常问题

问题背景 #

代码进入handleAmbiguousException方法但无法定位具体异常原因，该方法提示上游服务调用异常，但已确认上游服务无问题，推测异常出在retrieveConfiguration方法接收的func逻辑中。

添加日志后发现代码未进入doInternalMethod，但configuration.thenAccept(func)之前的日志正常输出，推测异常发生在该环节。目前仅能获取模糊异常信息：

• 堆栈仅显示：java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
• 异常字符串：java.util.concurrent.CompletionException: java.lang.NullPointerException
• 异常消息：MESSAGE java.lang.NullPointerException

现有代码片段 #

doSomething方法 #

public void doSomething(final HttpServletRequest httpServletRequest,
                        final AbstractCreateTokenRequest request,
                        final AsyncResponse asyncResponse){

    retrieveConfiguration(asyncResponse,
                        configuration -> doInternalMethod(asyncResponse, request, configuration), InternalConfiguration.class);
}

retrieveConfiguration方法 #

private <T extends SomeConfiguration> void
retrieveConfiguration(final AsyncResponse asyncResponse,
                      final Consumer<T> func,
                      final Class<T> configClass) {

    CompletionStage<T> configuration = configurationService.getConfiguration(configClass);

    configuration.thenAccept(func).
            exceptionally(throwable -> {
                handleAmbiguousException(asyncResponse, throwable);
                return null;
            });
}

doInternalMethod方法 #

private CompletionStage<Either<ServiceErrorResponse, TokenResponse>>
doInternalMethod(final AsyncResponse asyncResponse,
                    final AbstractCreateTokenRequest request,
                    final TokenConfiguration configuration) {

    final CompletionStage<Either<ServiceErrorResponse, TokenResponse>> stage = tokenCreator
            .createToken(configuration)
            .exceptionally(this::nestedException);
    stage.whenComplete((response, throwable) -> {
        MDC.clear();
    });
    setAsyncResponseFromEither(stage, asyncResponse, REQUEST_TIMEOUT_MS, request.toString());
    return stage;
}

handleAmbiguousException方法 #

private void
handleAmibguousException(final AsyncResponse asyncResponse,
                          final Throwable throwable) {
   asyncResponse.resume(ExceptionHandler.mapTheError(throwable));
}

代码改写与异常定位方案 #

核心思路是在thenAccept的消费逻辑中主动捕获异常，避免异常被CompletableFuture包装后丢失细节，同时增强日志输出精准定位问题。

改写后的关键代码 #

修正retrieveConfiguration方法

private <T extends SomeConfiguration> void retrieveConfiguration(final AsyncResponse asyncResponse,
                                                                 final Consumer<T> func,
                                                                 final Class<T> configClass) {
    CompletionStage<T> configuration = configurationService.getConfiguration(configClass);

    configuration.thenAccept(config -> {
        // 主动捕获func执行时的异常，避免被CompletableFuture包装
        try {
            func.accept(config);
        } catch (Throwable t) {
            // 输出完整堆栈日志，明确异常发生位置
            LOGGER.error("执行配置处理逻辑异常，配置类: {}", configClass.getName(), t);
            handleAmbiguousException(asyncResponse, t);
        }
    }).exceptionally(throwable -> {
        // 捕获配置服务调用本身的异常
        LOGGER.error("获取配置服务异常，配置类: {}", configClass.getName(), throwable);
        handleAmbiguousException(asyncResponse, throwable);
        return null;
    });
}

修正doSomething方法的类型转换逻辑

public void doSomething(final HttpServletRequest httpServletRequest,
                        final AbstractCreateTokenRequest request,
                        final AsyncResponse asyncResponse) {
    // 显式处理类型转换，避免隐式转换导致的NPE或类型转换异常
    retrieveConfiguration(asyncResponse,
            (InternalConfiguration configuration) -> {
                // 若类型不匹配，此处会直接抛出ClassCastException，便于定位
                TokenConfiguration tokenConfig = (TokenConfiguration) configuration;
                doInternalMethod(asyncResponse, request, tokenConfig);
            }, InternalConfiguration.class);
}

修正方法拼写错误

private void handleAmbiguousException(final AsyncResponse asyncResponse,
                                      final Throwable throwable) {
    asyncResponse.resume(ExceptionHandler.mapTheError(throwable));
}

定位逻辑说明 #

1. 主动捕获func执行异常：原代码中thenAccept(func)的异常会被CompletableFuture包装成CompletionException，丢失原始异常上下文，通过try-catch直接捕获并输出完整堆栈，可直接看到func中具体哪行代码抛出NPE。
2. 显式类型转换：如果InternalConfiguration与TokenConfiguration类型不匹配，显式转换会立即抛出ClassCastException，而非被包装后输出模糊异常，这可能是当前NPE的核心原因。
3. 分阶段日志：分别在配置获取、逻辑执行两个阶段添加日志，明确异常发生环节。

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