What’s New in Spring Boot 2.3.2? 88 Fixes, New Features & Upgrade Guide
Spring Boot 2.3.2, now available via repo.spring.io and Maven Central, introduces 88 bug fixes, enhanced health monitoring, configurable Docker image builds, reactive Elasticsearch checks, and resolves critical issues like reactor‑netty file descriptor limits and Redis Cluster health checks, urging users of 2.3.1 or 2.2.8 to upgrade.
Spring Boot 2.3.2, Spring Boot 2.2.9 and Spring Boot 2.1.16 are now available from repo.spring.io and Maven Central.
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>2.3.2.RELEASE</version>
<relativePath/>
</parent>This article focuses on the v2.3 release, which includes 88 bug fixes, feature enhancements, documentation improvements and dependency upgrades.
Release Notes
New Features
Enhanced Liveness/Readiness health monitoring with configurable probes.
Docker image build support with configurable parameters.
Added reactive Elasticsearch health check.
Bug Fixes and Optimizations
Upgrade to Reactor Dysprosium‑SR10 to resolve “Too many open files” issues that caused application crashes in v2.2.8 and v2.3.1.
Fixed reactive Redis health check failure caused by Redis Cluster.
Optimized graceful shutdown scenarios, supporting Spring Cloud applications.
Resolved welcome page (index.html) bypassing the “/” controller issue.
More logs can be found at https://github.com/spring-projects/spring-boot/releases/tag/v2.3.2.RELEASE.
Summary
If you are using Spring Boot v2.3.1 or v2.2.8, upgrade to the current version promptly.
This resolves service crashes caused by a reactor‑netty bug, affecting Spring Cloud Gateway and Spring Boot Admin applications.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Java Architecture Diary
Committed to sharing original, high‑quality technical articles; no fluff or promotional content.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.