引入spring-boot-starter-data-jpa后应用启动阻塞问题求助
Spring Boot引入JPA依赖后启动阻塞问题排查与解决
问题概述
引入spring-boot-starter-data-jpa依赖后,应用初始化阶段触发的HTTP请求(由apiV2OrderManagementOrderFiltersGet方法发起)出现阻塞:控制台输出请求日志及200响应日志后,应用无后续启动进展。方法内部使用block()同步等待WebClient响应,导致主线程死锁。
通过IntelliJ IDEA运行时应用完全停滞;使用mvn spring-boot:run可成功启动,但存在字体显示异常问题。项目基于Java 17开发,相关日志、代码及配置如下:
控制台日志
{"timestamp":"2025-01-30T19:09:27.309+03:00","level":"DEBUG","thread":"main","context":"default","message":"[2f5fb329] HTTP GET https://domen.ru/api/v2/orderManagement/order/filters","source":"org.springframework.web.reactive.function.client.ExchangeFunctions","application_name":"order-management","X-B3-TraceId":"679ba43657c761c850920b80eec8f134","X-B3-SpanId":"50920b80eec8f134"} {"timestamp":"2025-01-30T19:09:29.672+03:00","level":"DEBUG","thread":"reactor-http-nio-2","context":"default","message":"[2f5fb329] [044fea2d-1, L:/192.168.111.130:52242 - R:apidocs.canavara-group.ru/19.14.155.134:443] Response 200 OK","source":"org.springframework.web.reactive.function.client.ExchangeFunctions","application_name":"order-management","X-B3-TraceId":"679ba43657c761c850920b80eec8f134","X-B3-SpanId":"50920b80eec8f134"}
触发阻塞的代码
public List<Filter> apiV2OrderManagementOrderFiltersGet() throws WebClientResponseException { ParameterizedTypeReference<Filter> localVarReturnType = new ParameterizedTypeReference<Filter>() {}; return apiV2OrderManagementOrderFiltersGetRequestCreation().bodyToFlux(localVarReturnType).collectList().block(); }
数据库配置
spring.datasource.url=jdbc:postgresql://localhost:5432/order_management spring.datasource.username=order_management spring.datasource.password=order_management spring.datasource.driverClassName=org.postgresql.Driver spring.jpa.database-platform=org.hibernate.dialect.PostgreSQLDialect spring.liquibase.change-log=classpath:/db/liquibase-changelog.xml
已尝试方案及遗留问题
- 异步改造仍因必须调用
block()同步获取结果,阻塞问题未解决; - 替换为
spring-boot-starter-data-r2dbc后,出现Repository无法找到的错误。
解决方案
1. 核心阻塞问题:避免主线程调用block()
阻塞根源是应用初始化阶段的主线程调用了Reactor的block()方法,导致主线程等待Reactor异步线程的结果,而JPA初始化占用主线程资源形成死锁。
推荐方案:异步初始化
将初始化逻辑改为异步订阅,彻底避免主线程阻塞:
import org.springframework.stereotype.Component; import reactor.core.publisher.Flux; import java.util.List; import org.slf4j.Logger; import org.slf4j.LoggerFactory; @Component public class FilterInitializer { private static final Logger log = LoggerFactory.getLogger(FilterInitializer.class); private List<Filter> filters; // 原WebClient请求创建方法 private Flux<Filter> apiV2OrderManagementOrderFiltersGetRequestCreation() { // 保留原请求逻辑 return null; } @PostConstruct public void initFilters() { apiV2OrderManagementOrderFiltersGetRequestCreation() .collectList() .subscribe( loadedFilters -> { filters = loadedFilters; log.info("成功加载{}个过滤器", loadedFilters.size()); }, error -> log.error("初始化加载过滤器失败", error) ); } // 提供获取过滤器的方法,需处理初始化未完成的情况 public List<Filter> getFilters() { return filters; } }
临时替代方案(不推荐)
若必须同步获取结果,可指定超时时间避免永久阻塞:
return apiV2OrderManagementOrderFiltersGetRequestCreation() .bodyToFlux(localVarReturnType) .collectList() .block(Duration.ofSeconds(10)); // 设置超时时间
2. IDEA运行停滞问题解决
- 检查IDEA的VM运行参数,可添加
-Dreactor.schedulers.defaultBoundedElasticSize=20调整Reactor线程池大小; - 清理IDEA缓存:
File -> Invalidate Caches...,选择Invalidate and Restart后重新导入项目; - 确认IDEA使用的Java SDK为17版本。
3. R2dbc Repository找不到问题解决
- 确保Repository接口继承
R2dbcRepository而非JpaRepository:import org.springframework.data.r2dbc.repository.R2dbcRepository; public interface OrderRepository extends R2dbcRepository<Order, Long> {} - 在配置类上添加
@EnableR2dbcRepositories注解并指定Repository包路径:@Configuration @EnableR2dbcRepositories(basePackages = "com.yourpackage.repository") public class R2dbcConfig {} - 确认引入正确的R2dbc驱动依赖:
<dependency> <groupId>io.r2dbc</groupId> <artifactId>r2dbc-postgresql</artifactId> </dependency>
内容的提问来源于stack exchange,提问作者ShyhArd Rols
相关产品推荐
相关产品推荐

