Java实现非阻塞异步调用：解决Feign接口重复查询阻塞问题

1. 配置自定义异步线程池 #

先定义专属线程池，避免使用默认线程池引发资源耗尽问题：

@Configuration
@EnableAsync
public class AsyncThreadPoolConfig implements AsyncConfigurer {

    @Override
    public Executor getAsyncExecutor() {
        ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor();
        executor.setCorePoolSize(4);
        executor.setMaxPoolSize(8);
        executor.setQueueCapacity(100);
        executor.setThreadNamePrefix("Deploy-Checker-");
        executor.setRejectedExecutionHandler(new ThreadPoolExecutor.CallerRunsPolicy());
        executor.initialize();
        return executor;
    }
}

2. 封装异步部署状态检查逻辑 #

把原来同步循环调用Feign的逻辑抽成异步方法，用@Async标记交由自定义线程池执行：

@Service
public class DeployStatusService {

    private final ReleaseFeignClient releaseFeignClient;

    public DeployStatusService(ReleaseFeignClient releaseFeignClient) {
        this.releaseFeignClient = releaseFeignClient;
    }

    @Async
    public CompletableFuture<DeployStatus> checkStatusAsync(String releaseId) {
        DeployStatus currentStatus;
        do {
            currentStatus = releaseFeignClient.obtainInfoTaskFromRelease(releaseId);
            // 加短间隔避免高频调用下游服务
            try {
                Thread.sleep(1000);
            } catch (InterruptedException e) {
                Thread.currentThread().interrupt();
                throw new RuntimeException("部署状态检查被中断", e);
            }
        } while (!currentStatus.isCompleted());

        return CompletableFuture.completedFuture(currentStatus);
    }
}

3. 修改端点为非阻塞响应 #

让接口直接返回CompletableFuture，Spring MVC会自动处理异步响应，避免阻塞请求线程：

@RestController
@RequestMapping("/obtain-tasks-release")
public class DeployTaskController {

    private final DeployStatusService deployStatusService;

    public DeployTaskController(DeployStatusService deployStatusService) {
        this.deployStatusService = deployStatusService;
    }

    @GetMapping("/{releaseId}")
    public CompletableFuture<ResponseEntity<DeployStatus>> getDeployStatus(@PathVariable String releaseId) {
        return deployStatusService.checkStatusAsync(releaseId)
                .thenApply(ResponseEntity::ok)
                .exceptionally(ex -> ResponseEntity.status(HttpStatus.INTERNAL_SERVER_ERROR).build());
    }
}

4. 可选：使用Feign原生异步客户端 #

如果Feign版本支持，可直接定义异步Feign方法，进一步简化逻辑：

@FeignClient(name = "release-service")
public interface ReleaseFeignClient {

    @GetMapping("/api/releases/{releaseId}/tasks")
    CompletableFuture<DeployStatus> obtainInfoTaskFromRelease(@PathVariable String releaseId);
}

对应的检查逻辑调整为：

@Async
public CompletableFuture<DeployStatus> checkStatusAsync(String releaseId) {
    return CompletableFuture.supplyAsync(() -> {
        while (true) {
            try {
                DeployStatus status = releaseFeignClient.obtainInfoTaskFromRelease(releaseId).get();
                if (status.isCompleted()) {
                    return status;
                }
                Thread.sleep(1000);
            } catch (InterruptedException | ExecutionException e) {
                Thread.currentThread().interrupt();
                throw new RuntimeException("部署状态检查失败", e);
            }
        }
    });
}

关键注意事项 #

• 必须自定义线程池，默认SimpleAsyncTaskExecutor会每次创建新线程，高并发下易引发OOM。
• 循环调用需设置合理的间隔，避免对下游服务造成过大压力。
• 若前端需要实时结果，可返回任务ID，后端保存异步任务状态，前端通过ID轮询查询，避免长时间占用HTTP连接。

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