Oracle JDK 24 EOL September 2025 — Budget Now

Oracle JDK 24: What the September 2025 End-of-Life Means for Your Budget

Oracle JDK 24 is a non-LTS (Long-Term Support) release. It will reach end of life on September 16, 2025 — approximately 13 months from now. For organizations still running version 24 (latest update: 24.0.2), that date marks the end of both active support and security patches from Oracle.

If your fiscal year starts on or after July 1, this EOL lands squarely in the next budget cycle. Now is the time to decide how you will handle the transition — and to include that decision in the line item you submit for approval.

What the EOL Date Actually Means

After September 16, 2025:

• Oracle will no longer release public or commercial updates for JDK 24.
• No new security patches, bug fixes, or performance backports will be provided.
• Continued use of JDK 24 without support exposes your applications to unpatched vulnerabilities and compliance risks.

Because this is not an LTS release, the typical Oracle lifecycle for JDK 24 is short — approximately six months of active support from its general availability. Unlike LTS releases (e.g., JDK 17 or 21), there is no multi-year extended support option available from Oracle.

The Challenge with Upgrading at Scale

For many enterprises, upgrading from JDK 24 to a newer version (such as JDK 25 or an LTS release) is not a trivial project. It involves:

• Application compatibility testing — each JDK release introduces new language features, deprecations, and removals.
• Dependency validation — third-party libraries and frameworks must be updated to support the target JDK.
• Regression testing and performance tuning — runtime behavior can change across versions.
• Certification re-validation — internal security or compliance teams may require updated approvals.

Given the short cadence of non-LTS releases, many teams find they cannot complete the full migration lifecycle before the next EOL arrives. The result is either a scramble to upgrade late in the cycle, or a decision to skip one or more non-LTS versions and aim for an LTS release — which may still require significant effort.

Comparing Your Options

When the EOL date arrives, you have three paths:

1. Upgrade to a supported JDK

• Cost: Internal engineering time, testing infrastructure, potential productivity loss during cutover.
• Risk: Medium to high, depending on application complexity. The clock is fixed — missing the EOL means operating without patches.
• Timing: You need to have the migration completed by September 16, 2025 (or earlier to allow a buffer for validation).

2. Vendor extended support (if available)

Oracle’s extended support for non-LTS releases is not guaranteed. Historically, extended support has been offered only for select LTS versions. For JDK 24, you should confirm whether Oracle will offer any paid extension — the default assumption should be that no extended support exists.

3. Third-party support

Third-party maintenance providers can continue to deliver security patches and bug fixes for JDK 24 after Oracle’s official EOL. This gives you time to plan and execute an orderly migration without the pressure of an immovable deadline.

Typical cost comparison: Third-party support often costs a fraction of a full migration project and can be budgeted as an operating expense. It also eliminates the risk of running an unsupported JDK in production.

What to Include in Your Budget Request Now

To prepare for the upcoming fiscal year, consider adding the following line items to your budget proposal:

• Engineering hours for migration planning, testing, and cutover (if you plan to upgrade).
• Contingency funds in case migration takes longer than expected — for example, third-party support to cover a 6–12 month extension.
• Third-party support subscription for JDK 24, as a benchmark to compare against the cost of migrating or the risk of running unsupported.

Requesting a third-party support quote now gives you a concrete number to insert into your budget forecast, rather than an estimate. That makes the request easier to justify and approve.

Getting a Third-Party Support Quote as a Benchmark

Before you enter renewal or migration negotiations, it’s wise to know what third-party support would cost for your existing JDK 24 deployments. A quick conversation with a provider can yield a no-obligation quote that you can use as a comparison point — whether you ultimately choose to self-migrate, buy extended vendor support, or contract third-party maintenance.

Contact us to discuss your Oracle JDK environment and get a custom support quote that fits your budget cycle.