Ace8 is the modernization practice of AceMQ.24/7 support from AceMQ after go-live
Book an Assessment

On this page

  • Java
  • Oracle Database
  • Spring Boot
  • OpenRewrite
  • AWS Transform
  • GitHub Copilot
  • Tomcat
  • Spring
  • AWS
  • Java
  • Oracle Database
  • Spring Boot
  • OpenRewrite
  • AWS Transform
  • GitHub Copilot
  • Tomcat
  • Spring
  • AWS
The short answer

A Java 17 upgrade to 21 or 25 is usually a small change: most of the work is updating build plugins, bytecode libraries and agents that do not know the newer class-file versions, then running your regression suite. Pick 25 if your frameworks and vendors certify it, and 21 if a vendor has certified only 21.

ServiceJava upgradeWhat breaks, what a recipe can fix, and what needs a person.See the service

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.

AreaWhat changesUsual fix
Bytecode tools and agentsASM, Byte Buddy, Mockito, Lombok, JaCoCo and APM agents that do not know the newer class-file versionsUpdate them before anything else
Security ManagerPermanently disabled from Java 24; code that calls System.setSecurityManager failsReplace with another control
Dynamic agent loadingWarnings from Java 21, moving towards off by defaultLoad agents on the command line
Default charsetUTF-8 is the default from Java 18; code relying on the platform charset reads files differentlySet the charset explicitly
Application serversServer versions not yet certified for the newer JDK; Tomcat 11 requires Java 17 or laterCheck the vendor's support matrix
FrameworksSpring Boot 3 and Spring Framework 6 already run on 17; check the exact minor versions for 21 and 25Upgrade 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.

01

Java 21 is widely certified and adds virtual threads.

02

Java 25 is the newest LTS and the longest window

Verify agents and plugins first.

03

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:

java-17-upgrade-review.mdEngineer review
Findings
F-01Start the application with every agent and profiler attached and read the startup log for warnings.
F-02Compare file and stream output byte for byte where the charset might have mattered.
F-03Run a load test, because garbage-collection defaults and JIT behaviour differ between releases.
F-04Run the build from a clean cache in CI, not only on developer machines.
F-05Deploy to a copy of the production container image, not only the test host.
Illustrative sample, not a real client report

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

A rough guide to scope, not a price
Effort positionQualitative
Typical
LighterTypicalHeavier
Pushing the scope up
Nothing at the top setting
PriceQuote on request
Get a fixed price in the assessment

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.

01

Upgrade if tests exist and the frameworks are maintained.

02

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.

DistributionStandard support endsExtended or paid support endsSource
Oracle JDK 17September 2026 (Premier Support)September 2029 (Extended Support)Oracle Java SE Support Roadmap
Microsoft Build of OpenJDK 1730 Sep 2027None listedMicrosoft OpenJDK support
Eclipse Temurin 17At least 31 Oct 2027None listedAdoptium support
Red Hat build of OpenJDK 1731 Dec 2027 (full support)31 Jan 2029 (Extended Life Cycle Support)Red Hat OpenJDK life cycle
Azul Zulu 1730 Sep 202930 Sep 2031 (extended)Azul support roadmap
Amazon Corretto 1731 Oct 2029None listedAmazon Corretto

08 · Next step

How does Ace8 run a Java 17 upgrade?

Ace8 is the modernization practice of AceMQ.

  1. 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.

  2. 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.

FAQ

Frequently asked questions

Short answers to what buyers ask first. Something else on your mind? Ask an engineer.

Java 25 if your frameworks and vendors support it, Java 21 if a vendor has certified only 21. Both are LTS releases with support into the 2030s.

Start here

Know the cost before anything moves.

A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.

Inventory
Every application, its stack and what it depends on.
Risk score
Where a change is likely to break, ranked.
Phased plan
What moves first, which tools lead, and the fixed price.

Get in touch

Talk to a modernization engineer.

Tell us what you run today. An engineer, not a sales script, replies within one business day.

305-204-2607info@ace8.io

66 W. Flagler St. 9th Floor
Miami, FL 33130

What are you moving off? *

Fixed price. Scope and cost before any migration starts.