Oracle JDK 23 EOL March 2025: Plan Migration or Support

The End-of-Life Date That Falls Into Your Next Fiscal Year

Oracle JDK 23 will reach its end of life on March 18, 2025, when both general availability and active support end. This is not a Long-Term Support (LTS) release, so there is no extended support window from Oracle beyond that date — patches, security fixes, and technical assistance will stop unless you purchase a separate extended-support contract.

For planning purposes, that date is roughly 13 months from now. For many organizations, that places the transition right inside the next fiscal year. Budget decisions for FY2025 migration or support costs need to be locked in during the current cycle.

What the EOL Date Actually Means for Your JDK Environment

After March 18, 2025:

• Oracle will stop releasing public updates (including security patches) for JDK 23.
• Critical bug fixes will no longer be provided by Oracle.
• Oracle support engineers will not assist with JDK 23 issues.

The latest release in the 23 line is version 23.0.2. Teams still on earlier builds should plan upgrades to 23.0.2 before the cutoff, but that alone does not extend the lifecycle — all of JDK 23 hits EOL on the same date.

What Upgrading from JDK 23 Typically Involves

Migrating off JDK 23 usually means moving to the next non-LTS release (JDK 24, which will be available) or to an LTS release such as JDK 21 or JDK 17. Either path involves:

• Regression testing of application servers, libraries, and custom code
• Updating build scripts, CI/CD pipelines, and container images
• Validating third-party dependencies for compatibility with the new version
• Coordinating with application teams to schedule downtime or blue/green deployments

At enterprise scale, even a straightforward JDK upgrade can take 4–6 months of planning, testing, and phased rollout across environments. That timeline is tight if you start now.

Why Teams Often Can’t Migrate in Time

The most common blockers include:

• Vendor applications that are not yet certified for the target JDK version
• Legacy code with unsupported API calls that fail compilation on newer releases
• Overlapping upgrade cycles (e.g., database upgrades, OS migrations) that compete for the same QA resources
• Budget cycles that already allocated funds for other priorities

If any of these apply, the March 2025 date will arrive before the migration is finished. That means running an unsupported JDK in production — a risk most compliance teams will flag.

Comparing the Cost of Migration vs. Extended Support vs. Third-Party Support

Migration costs are primarily internal engineering time plus potential vendor licensing for new tools. The cost can be high but is a one-time investment.

Oracle extended support (for non-LTS releases) is available only through a separate commercial agreement. Pricing is per-processor and typically increases each year. It maintains access to patches and support but ties you to Oracle’s schedule.

Third-party support for Oracle JDK 23 can extend the safe runway without requiring an immediate migration. A provider like 3rd Party Support can deliver independent security patches and technical support for the JDK version you already have, often at a fraction of extended-support costs. That gives your team breathing room to plan the migration on your own timeline.

What to Put in the Budget Request Now

Your budget proposal should include one of three line items:

1. Migration costs — internal engineering hours, testing tool licenses, potential vendor re-certifications.
2. Oracle extended support — contact your Oracle account team for a renewal quote covering JDK 23 past March 2025.
3. Third-party support — a fixed-term contract covering your existing JDK 23 deployments.

Many teams find it useful to get a third-party support quote as a benchmark before entering renewal negotiations with Oracle. That way you know the floor price and can compare options objectively.

Get a Third-Party Support Quote Before Renewal Talks

We recommend requesting a custom quote from 3rd Party Support for your Oracle JDK 23 environment now, while you’re still in the budget-planning window. With a firm number in hand, you can make an apples-to-apples comparison against migration or vendor extended support — and have a fallback option ready if internal migration timelines slip.

For more detail on Oracle’s Java lifecycle, see our Oracle software support page.