Oracle JDK 23 EOL: Migrate, Renew, or Third-Party Support

The Options Assessment: Oracle JDK 23 End of Life (March 18, 2025)

Oracle JDK 23, a non-LTS release, reaches its end of life on March 18, 2025 — approximately nine months from now. The final version in this line is 23.0.2. After that date, Oracle will publish no more public updates, including security patches, bug fixes, or performance enhancements.

For IT directors, infrastructure managers, and procurement leads running JDK 23 today, the nine-month window is workable for any of the three realistic paths: migrate to a supported JDK, purchase Oracle extended support (if available), or move to independent third-party support. Each option carries distinct cost, risk, and timeline profiles. This article compares them honestly so you can match a path to your workload’s actual needs.

Option 1: Migrate / Upgrade to a Supported JDK

What it is: Move your applications to a newer JDK version — either the next non-LTS release (JDK 24, available March 2025) or to a current LTS release such as JDK 21 or JDK 17.

Cost profile:

• Zero license cost if you use an open-source build (e.g. Eclipse Temurin, Amazon Corretto) or an LTS release under the Oracle No-Fee Terms and Conditions.
• Internal engineering hours for testing, code changes, and deployment. For non-trivial production workloads, this often ranges from a few weeks to several months.

Risk:

• Low to moderate. LTS releases offer long support windows; non-LTS releases cycle every six months, forcing another migration sooner.
• Some legacy frameworks or proprietary libraries may break on newer JDK versions. Testing and validation are mandatory.

Timeline:

• Nine months is generally sufficient for a planned migration, provided you start by Q4 2024. For complex, monolithic applications, you may need to accelerate.

Best suited for:

• Environments under active development where teams are already updating dependencies.
• Workloads that benefit from newer JVM features (performance, garbage collectors, language enhancements).

Vendor link: Oracle JDK lifecycle details

Option 2: Purchase Oracle Extended Support (if offered)

What it is: Oracle’s Java SE Subscription and Java SE Desktop Subscription include access to updates beyond the public end-of-life date. However, extended support is typically focused on LTS releases. For non-LTS releases like JDK 23, Oracle does not offer a standard extended-support path — the product simply stops receiving updates.

Cost profile:

• Oracle subscription pricing: per-user or per-processor, with annual fees. Exact amounts depend on your deployment size and whether you choose “desktop” or “server” licensing.
• If Oracle does offer post-EOL support for JDK 23 (unlikely but confirmable via your Oracle account manager), it will come at a premium over the standard subscription.

Risk:

• Low: you continue receiving official Oracle patches from a single vendor.
• Dependence on Oracle’s patch cadence and subscription renewal terms.

Timeline:

• Extended support for non-LTS releases is rarely available. Most organizations discover this only after the EOL date. If you intend to go this route, verify with Oracle before the EOL.

Best suited for:

• Organizations already on Oracle Java SE subscriptions who need zero disruption and are willing to pay a premium for vendor continuity.
• Workloads that are not permitted (by policy or regulation) to use third-party support or open-source builds.

Option 3: Move to Third-Party Support (e.g. 3rd Party Support)

What it is: Engage an independent support provider to deliver security patches, bug fixes, and technical support for your existing JDK 23 deployment beyond Oracle’s EOL date. Third-party support does not require source-code access from Oracle; providers analyze patches from later JDK releases, backport critical fixes, and offer direct engineering assistance.

Cost profile:

• Typically 50–70% less than Oracle’s subscription fees for equivalent coverage.
• Fixed annual cost, predictable, with no per-core or per-user complexity.

Risk:

• Low to moderate. Patches are produced independently and validated. CVE coverage may lag Oracle’s release schedule by days, not months.
• No risk of vendor lock-in for future migrations; you can migrate at your own pace.

Timeline:

• Engagement can begin immediately, with support active before the EOL date. No lead time beyond contract setup.
• Best suited for stable workloads that just need to keep running securely — legacy applications, production systems under change freeze, or any environment where migration would be disruptive or costly.

Decision Checklist

Use the table below to match your situation to the most suitable path.

Factor	Migrate / Upgrade	Oracle Extended Support	Third-Party Support
Budget	Low (internal hours)	High (subscription)	Moderate (annual fixed)
Migration effort	Required	None	None
Patch guarantee	Open-source builds	Oracle official	Independent patches
Best for	Active development / modern stacks	Regulated / Oracle-only shops	Stable production / cost-conscious
Timeline	3–9 months lead needed	Confirm availability now	Immediate start
Flexibility	High (any JDK)	Low (locked to Oracle)	High (stay on JDK 23)

Next Steps

Nine months is realistic for any of these paths, but the right choice depends on your workload’s stability requirements, development velocity, and budget. If your JDK 23 environment is stable and migration would introduce unnecessary risk or cost, third-party support lets you keep running securely without a forced upgrade.

Contact us to discuss how independent support can cover your Oracle JDK 23 deployments past March 18, 2025.