01 · What changes
What changes when you upgrade from Java 17 to 21 or 25?
See Java 21 features and Java 25 LTS for what the newer releases add. The Java upgrade service describes how Ace8 delivers the move.
| Area | What changes | Usual fix |
|---|---|---|
| Bytecode tools and agents | ASM, Byte Buddy, Mockito, Lombok, JaCoCo and APM agents that do not know the newer class-file versions | Update them before anything else |
| Security Manager | Permanently disabled from Java 24; code that calls System.setSecurityManager fails | Replace with another control |
| Dynamic agent loading | Warnings from Java 21, moving towards off by default | Load agents on the command line |
| Default charset | UTF-8 is the default from Java 18; code relying on the platform charset reads files differently | Set the charset explicitly |
| Application servers | Server versions not yet certified for the newer JDK; Tomcat 11 requires Java 17 or later | Check the vendor's support matrix |
| Frameworks | Spring Boot 3 and Spring Framework 6 already run on 17; check the exact minor versions for 21 and 25 | Upgrade to the minor each vendor certifies |
02 · Target
Should you upgrade Java 17 to 21 or to 25?
Go to Java 25 if your frameworks and vendors support it, and Java 21 if a vendor has certified only 21. Both are LTS releases with long windows.
Java 21 is widely certified and adds virtual threads.
Java 25 is the newest LTS and the longest window
Verify agents and plugins first.
Oracle JDK 17 updates from 15 October 2024 are under the Java SE OTN licence, free only for personal, development and other permitted uses. Oracle applied the same change to Java 21 for updates from 20 October 2026 and points users wanting a permissive Oracle JDK to Java 25 or later.
03 · Tools
Which tools automate a Java 17 upgrade?
OpenRewrite handles the repeatable build and API edits, and AWS Transform and GitHub Copilot app modernization cover what recipes miss. At this step the tests matter more than the tools.
04 · Testing
What test plan catches what breaks in a Java 17 upgrade?
Run the full regression suite on the new JDK with the same build, then the checks that suites often miss:
05 · Effort
What drives the effort of a Java 17 upgrade?
Effort follows the number of applications and the age of their agents and libraries. A fixed-price assessment gives a per-application estimate. The drivers:
Test coverage and the time the suite takes to run
Agents and bytecode tools in the build and at runtime
Use of the Security Manager or dynamic agent loading
Application server and framework certification for the target Java
How many applications share a build parent or CI image
06 · Decision
Should you upgrade or rewrite a Java 17 application?
Upgrade. A Java 17 application is rarely a rewrite candidate because of its Java version; rewrite only when the design blocks changes you need anyway.
Upgrade if tests exist and the frameworks are maintained.
Consider a rewrite or refactor only when architecture, not runtime, is the problem. See rehost, replatform, refactor or rewrite.
07 · 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 17 for now? OSSeva covers that.
| Distribution | Standard support ends | Extended or paid support ends | Source |
|---|---|---|---|
| Oracle JDK 17 | September 2026 (Premier Support) | September 2029 (Extended Support) | Oracle Java SE Support Roadmap |
| Microsoft Build of OpenJDK 17 | 30 Sep 2027 | None listed | Microsoft OpenJDK support |
| Eclipse Temurin 17 | At least 31 Oct 2027 | None listed | Adoptium support |
| Red Hat build of OpenJDK 17 | 31 Dec 2027 (full support) | 31 Jan 2029 (Extended Life Cycle Support) | Red Hat OpenJDK life cycle |
| Azul Zulu 17 | 30 Sep 2029 | 30 Sep 2031 (extended) | Azul support roadmap |
| Amazon Corretto 17 | 31 Oct 2029 | None listed | Amazon Corretto |
08 · Next step
How does Ace8 run a Java 17 upgrade?
Ace8 is the modernization practice of AceMQ.
- 01
AceMQ engineers swap licensed Oracle JDKs for an OpenJDK build where needed, then move applications to 21 or 25 with OpenRewrite recipes and engineer-reviewed changes. AceMQ supports the stack after go-live.
- 02
Get a Java upgrade estimate through the modernization assessment, which lists every JDK vendor and version per application. Related: Java 11 upgrade and Java 8 upgrade.