Oracle JDK 22 End of Life September 17, 2024 — Options

Understanding the Oracle JDK 22 Lifecycle Endpoint

Oracle JDK 22 is a non-LTS (short-term) release, which means its support lifecycle is deliberately brief. Oracle will end both flagship and active support on September 17, 2024 — roughly nine months from the release date of March 19, 2024. The latest and final update in this line is version 22.0.2, after which no further public patches will be issued by Oracle for JDK 22.

For IT managers, this tight window presents a clear decision point. Nine months is a comfortable runway to plan and execute a strategy, but the right choice depends on your deployment’s context: is this a stable, low-risk workload that simply needs to keep running, or is it a platform under active development where API churn is acceptable?

The Three Realistic Paths

1. Migrate or Upgrade to an LTS Release

What it is Move your runtime to an Oracle JDK Long-Term Support (LTS) release, such as JDK 17 or JDK 21. Both are supported by Oracle until at least 2029 and 2032 respectively.

Cost profile

• No incremental licensing cost if you are already on an Oracle Java SE subscription.
• Internal engineering effort: testing for API/behavior changes between JDK 22 and your target LTS. JDK 22 is a short-term release with several preview features and experimental changes; a regression audit is advisable.
• Timeline: 2–4 months for a thorough test-and-deploy cycle in medium-to-large environments.

Risk

• Low for codebases that do not use preview features (e.g., scoped values, record patterns).
• Moderate if your application depends on incubator modules or libraries that have not been updated for the target LTS.

Best suited for

• Platforms under active development where you can adjust code to the LTS version.
• Teams that already have a CI/CD pipeline and can absorb a minor refactor window.

2. Purchase Extended Support from Oracle

What it is Oracle’s Java SE Subscription includes the option to receive quarterly critical-patch updates (CPUs) for non-LTS releases after their official end-of-life date, but only if you also have an active subscription covering an LTS release.

Reality check For JDK 22, Oracle does not offer standalone extended support; the “extended” support window applies only to LTS releases. Short-term releases like JDK 22 are not eligible for post-EOL patches from Oracle. This means “extended support” as a standalone purchase is effectively unavailable for this version.

What this means for you If you stay on JDK 22 beyond September 2024 without a subscription to an LTS release, you will receive no updates from Oracle at all. The only way to get security patches from Oracle is to upgrade to an LTS release under subscription. Thus, this path collapses into the “migrate/upgrade” option above for practical purposes.

3. Move to Third-Party Support

What it is Partner with a third-party maintenance provider (such as 3rd Party Support) that continues to backport security patches and critical bug fixes for JDK 22 well past Oracle’s EOL date.

Cost profile

• Typically 50–70% less than the equivalent Oracle subscription fee for an LTS release.
• No requirement to purchase a second product or subscription tier.
• Covers the exact version you have now: no re-qualification of your workload.

Risk

• Low for stable production workloads. You do not change your JDK version, just who supplies the updates.
• Vendor dependency: ensure the provider has proven capability for JDK patching. (3rd Party Support has been delivering JVM patches for a decade.)

Timeline You can transition within weeks. There is no code change; the service layer sits between your JDK distribution and the upstream patch stream.

Best suited for

• Legacy or compliance-constrained environments where re-certifying on a new JDK version is too expensive or slow.
• Stable, containerised workloads where the JDK version is a certified component (e.g., in regulated industries like finance or healthcare).
• Any team that values operational continuity over feature velocity.

Decision Checklist

Use this rapid assessment to map your environment to the right path.

Criterion	Migrate/Upgrade to LTS	Third-Party Support
Workload is stable, no active dev	❌	✅
Requires new Oracle licensing	✅ (LTS subscription)	❌
Can re-certify within 6 months	✅	✅
Uses preview or incubator features in JDK 22	⚠️ (risk)	✅ (no change)
Budget for total cost of ownership	Moderate upfront	Lower recurring
Regulatory/internal freeze on JDK version	❌	✅
Want to keep latest JDK features	✅	❌

Decision rule of thumb

• If your app uses no preview features and you have a mature CI pipeline → migrate to an LTS.
• If your app is closed for changes, running on containers, or cost-sensitive → choose third-party support.
• If you need both security patches and new features → migrate to an LTS and plan a future upgrade. Not even third-party support can add new APIs to JDK 22.

Acting Within the Nine-Month Window

September 17, 2024 is firm. A nine-month lead gives you time to follow a structured decision process:

1. Audit your JDK 22 usage — how many servers, containers, and applications depend on it.
2. Catalog blockers — does any library or framework mandate JDK 22 specifically?
3. Evaluate third-party support — request a sample patch delivery and SLA.
4. Execute the transition by August 2024 at the latest, to avoid the last-minute rush.

If you decide that third-party support is the right fit for your stable workloads, contact us to discuss a tailored plan. Our team can have you on a supported JDK 22 path within two weeks of agreement.

Where to learn more

• Oracle lifecycle data for JDK
• Oracle JDK on 3rdpartysupport.com

---

This article is editorial content. It is not sponsored or approved by Oracle Corporation. Oracle, Java, and JDK are registered trademarks of Oracle and/or its affiliates.