Oracle JDK 22 EOL Sept 17, 2024 – Budget for Migration or Support

Oracle JDK 22 reaches end of life in 13 months — what that means for your budget cycle

Oracle JDK 22 is set to reach its end of life on September 17, 2024, with no extended support period. Because this is not a Long-Term Support (LTS) release, the vendor will provide no updates, security patches, or bug fixes after that date. The latest version in this line is 22.0.2.

For organizations running Oracle JDK 22 in production, this date lands in the next fiscal year for most budget cycles. That means the decision to migrate, contract extended support, or engage a third-party support provider must be made now — before budget lines are finalized.

What the end‑of‑life date actually means

After September 17, 2024, Oracle will no longer release:

• Security patches (CVE fixes)
• Bug fixes
• Performance enhancements
• Technical support for JDK 22

Any JDK 22 instances remaining in production after that date will be running without vendor protection against newly discovered vulnerabilities. Compliance requirements, such as PCI DSS or SOC 2, may treat unsupported software as a finding, which could affect audit outcomes.

Upgrading at enterprise scale — why it often takes longer than expected

Migrating from one JDK release to the next is not a trivial flag‑flip in most enterprise environments. The typical workstream includes:

• Identifying all dependencies (libraries, frameworks, application servers) that rely on JDK 22
• Testing each application for compatibility with the target JDK version
• Updating container images, CI/CD pipelines, and deployment scripts
• Coordinating change windows across dozens or hundreds of applications
• Validating performance before cutover

For a mid‑sized enterprise with more than 50 applications, a full migration can take six to nine months from start to finish — even when the team is well‑resourced. With only 13 months until the EOL window closes, there is little margin for delay.

Comparing the cost scenarios

When preparing next year’s budget, you’ll typically consider three paths:

1. Migrate to a supported JDK

This is the “clean” option but carries hidden costs: internal engineering hours, potential downtime during cutovers, and the risk of compatibility regressions. Budget line items should include dedicated developer and QA time, plus any needed tool or environment changes.

2. Purchase Oracle extended support (if available)

For non‑LTS releases like JDK 22, Oracle does not offer an extended support window. If your organization instead chooses to move to an LTS release (e.g., JDK 21) and purchase extended support for that version, the cost can be substantial — typically 20–50% of the original license fee per year, escalating annually. This option buys time but not permanence.

3. Third‑party support

Third‑party support providers can cover JDK 22 past the vendor’s end‑of‑life date, delivering security patches and technical break‑fix support without requiring a version migration. This is often priced at 30–50% of the vendor’s annual support fee and keeps the existing deployment unchanged.

What to include in your budget request now

To give your finance team a concrete figure, the current budget request should include:

• Estimated internal migration hours (development, QA, operations)
• Any licensing costs for moving to an LTS release
• Cost of Oracle extended support (if applicable)
• A benchmark third‑party support quote for comparison

The last item is particularly valuable: a third‑party support quote locks in today’s pricing and serves as a reference point if you need to negotiate vendor renewal or extended support terms later.

Getting a third‑party support quote as a benchmark

Before you enter renewal talks with Oracle, it is standard practice to have an alternative cost at hand. Third‑party support for Oracle JDK 22 can be priced to match your current deployment size, and contracts typically include security backporting and responsive technical support — no lock‑in, no forced upgrades.

Contact our team at the link below for a confidential, no‑obligation quote. Use it as a benchmark to decide whether migration, extended vendor support, or third‑party support makes the most sense for your next fiscal year. Contact us to start the conversation.

---

All lifecycle dates sourced from endoflife.date/oracle-jdk.