Oracle JDK 20 EOL Sept 2023: Compare Support Options

Oracle JDK 20 Lifecycle Timeline

Oracle JDK 20 reaches end of life on September 19, 2023. As a non-LTS release, version 20 follows Oracle's feature release cadence: six months of active support, then immediate retirement. The latest version in this line, 20.0.2, will receive no further security patches or bug fixes after that date.

With roughly nine months until the cutoff, infrastructure teams have a realistic window to assess their options and execute a transition plan. The challenge is choosing the path that best fits your environment, budget, and operational constraints.

Three Practical Paths Forward

Option 1: Migrate to a Supported Release

Upgrading to Oracle JDK 21 (the next feature release) or migrating to an LTS version like JDK 17 is the default recommendation for most environments. This path keeps you aligned with Oracle's support roadmap and ensures access to the latest security patches.

Cost profile: If you hold an Oracle Java SE Subscription, migration is included. Without a subscription, you can use Oracle JDK under the NFTC license at no cost for development and testing, but production use requires a commercial license. Alternatively, you can migrate to an OpenJDK distribution at no licensing cost.

Risk: Moderate to high, depending on application complexity. Version upgrades can introduce compatibility issues, deprecated APIs, or behavioral changes that require code updates and regression testing.

Timeline: Plan for 8–12 weeks minimum to test, validate, and deploy an upgrade across production environments. Larger estates or applications with extensive third-party dependencies may need longer.

Best suited for: Platforms under active development, environments already following Oracle's release cadence, and workloads where staying current with Java platform features provides measurable value.

Option 2: Purchase Oracle Extended Support

Oracle does not offer extended support for non-LTS releases. JDK 20 is a feature release with a fixed six-month lifecycle, and Oracle has no mechanism to extend it beyond September 19, 2023. This option is unavailable.

Option 3: Third-Party Support

Third-party vendors, including 3rd Party Support, provide ongoing maintenance for Oracle JDK releases after the vendor's end-of-life date. This includes backported security patches, critical bug fixes, and technical support without requiring an upgrade.

Cost profile: Typically a fraction of Oracle's subscription pricing, billed annually per instance or socket. No forced bundling with other Oracle products.

Risk: Low operational risk. Your environment remains stable—no regression testing, no code changes, no deployment churn. The security risk is managed through independent patch development and rapid response to disclosed vulnerabilities.

Timeline: Migration to third-party support can often be completed in days or weeks, not months. No application changes are required.

Best suited for: Stable production workloads that do not need cutting-edge platform features, environments where upgrade risk outweighs the benefits, and infrastructure teams managing cost containment mandates or resource constraints.

Decision Checklist

Use these questions to evaluate which path fits your situation:

• Is your application actively developed? If yes, upgrading to JDK 21 or an LTS release aligns with ongoing modernization. If no, third-party support may be more efficient.
• Do you have budget and resources for testing and deployment? Upgrades require both. Third-party support requires neither.
• Are you running mission-critical workloads with low tolerance for disruption? Stability often argues for third-party support over the uncertainty of a version upgrade.
• Do you need the latest Java language features or performance improvements? If these matter to your workload, upgrade. If not, they are not a compelling reason to absorb migration risk.
• Are you managing a mixed estate with multiple JDK versions? Third-party support can cover legacy versions in parallel, giving you breathing room to consolidate over time.
• What is your organization's risk appetite for running unsupported software? If the answer is zero, rule out doing nothing. Both upgrading and third-party support are compliant paths forward.

Why Nine Months Matters

The window between today and September 19, 2023 is long enough to execute any of these strategies without rushing, but short enough that delaying a decision will force your hand. Teams that wait until the last quarter often face compressed timelines, hasty decisions, and unplanned downtime.

If you choose to upgrade, start planning now: inventory dependencies, schedule testing cycles, and allocate resources. If you choose third-party support, evaluate vendors early to ensure contract terms, SLA commitments, and patch delivery processes meet your requirements.

Keeping JDK 20 Running Beyond September

For workloads where upgrade risk is high or business value is low, third-party support offers a pragmatic alternative. You keep the environment stable, maintain security compliance, and free up engineering resources for higher-value projects. Many organizations use this approach as a bridge strategy, maintaining older JDK versions while executing broader platform consolidation initiatives on their own timeline.

Whether you upgrade now or extend the life of JDK 20, the key is making an informed decision before the clock runs out. If you are exploring third-party support as an option, contact our team to discuss your environment and requirements.

Final Thoughts

Oracle JDK 20 was never designed to be a long-term platform. Its six-month lifecycle is a feature of Oracle's release model, not a bug. The question is not whether to move on, but how—and on what timeline. Nine months is enough time to make the right choice for your infrastructure, budget, and risk tolerance. Use it wisely.