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

Java 11 upgrade: moving to 21 or 25.

Less work than leaving Java 8. The Java EE modules are already gone; what is left is encapsulation, build tooling and framework versions.

AceMQ engineering team4 min readEngineer-reviewedUpdated

On this page

  • Java
  • Spring Boot
  • Jakarta EE
  • Oracle Database
  • OpenRewrite
  • AWS Transform
  • GitHub Copilot
  • Spring
  • Maven
  • Gradle
  • AWS
The short answer

A Java 11 upgrade goes to Java 21 or 25, with Java 17 only when a vendor product stops there. It is a smaller step than leaving Java 8, because the Java EE modules are already out of the JDK; the breaks come from strong encapsulation, outdated build plugins and agents, and Spring Boot 3, which needs Java 17 or later.

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

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.

AreaWhat breaksUsual fix
JDK internalsStrong encapsulation in Java 17: --illegal-access is gone and libraries that reflect into java.base fail at runtimeUpdate the library; --add-opens only as a stopgap
Spring BootSpring Boot 3 requires Java 17 and the jakarta namespace; most Java 11 applications run Spring Boot 2Plan the Java and Spring moves together; see Spring Boot 3 migration
Removed APIsNashorn (removed in Java 15) and the Security Manager (disabled from Java 24)Replace the script engine or the control
Bytecode tools and agentsASM, Byte Buddy, Mockito, Lombok, JaCoCo and APM agents older than the target class-file versionUpdate them first
Default charsetUTF-8 became the default in Java 18; code that relied on the platform charset reads files differentlySet the charset explicitly
Build and runtimeMaven or Gradle plugins, CI images, container bases and JVM flagsEdit 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.

01

Java 17

The minimum for Spring Boot 3. Check the vendor dates below, because free OpenJDK 17 fixes end in late 2027.

02

Java 21

Widely certified. Oracle JDK 21 updates from 20 October 2026 are under the OTN licence, so most teams use an OpenJDK build.

03

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

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

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.

01

Upgrade if tests exist, the frameworks are maintained and the team understands the code.

02

Rewrite if a framework has no successor or the architecture blocks changes you need whatever the Java version.

03

Otherwise upgrade first, then refactor the parts that hurt

See rehost, replatform, refactor or rewrite.

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.

DistributionStandard support endsExtended or paid support endsSource
Oracle JDK 11September 2023 (Premier Support)January 2032 (Extended Support)Oracle Java SE Support Roadmap
Red Hat build of OpenJDK 1131 Oct 2024 (full support)31 Jan 2032 (Extended Life Cycle Support)Red Hat OpenJDK life cycle
Eclipse Temurin 11At least 31 Oct 2027None listedAdoptium support
Microsoft Build of OpenJDK 1130 Sep 2027None listedMicrosoft OpenJDK support
Amazon Corretto 1131 Jan 2032None listedAmazon Corretto
Azul Zulu 1131 Jan 203231 Jan 2034 (extended)Azul support roadmap

07 · Next step

How does Ace8 run a Java 11 upgrade?

Ace8 is the modernization practice of AceMQ.

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

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

FAQ

Frequently asked questions

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

To 21 or 25 if your frameworks and vendors certify them. The work is similar to moving to 17, and the support window is years longer.

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.