01 · What breaks
What breaks when you upgrade from Java 11 to 21 or 25?
The Java upgrade service describes how Ace8 delivers these changes.
| Area | What breaks | Usual fix |
|---|---|---|
| JDK internals | Strong encapsulation in Java 17: --illegal-access is gone and libraries that reflect into java.base fail at runtime | Update the library; --add-opens only as a stopgap |
| Spring Boot | Spring Boot 3 requires Java 17 and the jakarta namespace; most Java 11 applications run Spring Boot 2 | Plan the Java and Spring moves together; see Spring Boot 3 migration |
| Removed APIs | Nashorn (removed in Java 15) and the Security Manager (disabled from Java 24) | Replace the script engine or the control |
| Bytecode tools and agents | ASM, Byte Buddy, Mockito, Lombok, JaCoCo and APM agents older than the target class-file version | Update them first |
| Default charset | UTF-8 became the default in Java 18; code that relied on the platform charset reads files differently | Set the charset explicitly |
| Build and runtime | Maven or Gradle plugins, CI images, container bases and JVM flags | Edit each one; recipes do not touch them |
02 · Target
Should you go from Java 11 to 17, 21 or 25?
Go to Java 21 or 25 if your frameworks and vendors certify them, because the work is similar to moving to 17 and the window is years longer. Choose 17 only when a vendor product is certified to 17 and no later.
Java 17
The minimum for Spring Boot 3. Check the vendor dates below, because free OpenJDK 17 fixes end in late 2027.
Java 21
Widely certified. Oracle JDK 21 updates from 20 October 2026 are under the OTN licence, so most teams use an OpenJDK build.
Java 25
The newest LTS. Check every agent and plugin first; some lag new releases. See Java 25 LTS.
03 · Tools
Which tools automate a Java 11 upgrade?
OpenRewrite, AWS Transform and GitHub Copilot app modernization automate the mechanical part. Run recipes first because they are repeatable, use an AI-assisted tool on what is left, then test and review.
04 · Effort
What drives the effort of a Java 11 upgrade?
Effort follows the state of each application rather than the estate total. A fixed-price assessment gives a per-application estimate. The drivers:
Whether the application is also on Spring Boot 2, which adds the javax to jakarta rename
Test coverage, which is how you know behaviour held
Libraries that reflect into JDK internals and have no release for the target Java
Agents and bytecode tooling in the build and at runtime
Application server certification for the target Java
How many applications share a build parent or CI image, which lets one fix cover many
05 · Decision
Should you upgrade or rewrite a Java 11 application?
Upgrade when the design still fits and rewrite when the design is the blocker. Java 11 code is usually recent enough that upgrading is the default.
Upgrade if tests exist, the frameworks are maintained and the team understands the code.
Rewrite if a framework has no successor or the architecture blocks changes you need whatever the Java version.
Otherwise upgrade first, then refactor the parts that hurt
06 · Reference
Support dates by vendor
Dates checked 17 Nov 2026. Oracle and Red Hat dates were read on their own pages; the others come from endoflife.date, which links each vendor's page. Confirm with your vendor before you plan around a date.
Need to stay on Java 11 for now? OSSeva covers that.
| Distribution | Standard support ends | Extended or paid support ends | Source |
|---|---|---|---|
| Oracle JDK 11 | September 2023 (Premier Support) | January 2032 (Extended Support) | Oracle Java SE Support Roadmap |
| Red Hat build of OpenJDK 11 | 31 Oct 2024 (full support) | 31 Jan 2032 (Extended Life Cycle Support) | Red Hat OpenJDK life cycle |
| Eclipse Temurin 11 | At least 31 Oct 2027 | None listed | Adoptium support |
| Microsoft Build of OpenJDK 11 | 30 Sep 2027 | None listed | Microsoft OpenJDK support |
| Amazon Corretto 11 | 31 Jan 2032 | None listed | Amazon Corretto |
| Azul Zulu 11 | 31 Jan 2032 | 31 Jan 2034 (extended) | Azul support roadmap |
07 · Next step
How does Ace8 run a Java 11 upgrade?
Ace8 is the modernization practice of AceMQ.
- 01
AceMQ engineers run OpenRewrite recipes for the Java and Spring Boot 3 steps, use AI-assisted tools on what the recipes miss, and review every change against your tests. AceMQ supports the stack after go-live.
- 02
Get a Java upgrade estimate through the modernization assessment. It lists your JDK vendors, versions and the frameworks that pin each application, then proposes a target. Related: Java 8 upgrade and Java 17 upgrade.