Oracle JDK 22 EOL: Sept 17, 2024 – Migration Options

Six Months to Oracle JDK 22 End of Life – What That Means for Your Migration Timeline

Oracle JDK 22 reaches end of life (EOL) on September 17, 2024. Unlike long-term support (LTS) releases, JDK 22 will receive no further public updates or security patches after that date. The latest version in this line is 22.0.2. If your organization still relies on JDK 22 in production, the window for a comfortable migration is closing faster than it may seem.

A Realistic Migration Timeline Worked Backwards from September 17, 2024

September 17 sounds distant, but procurement cycles, change freezes, and testing consume most of that buffer. Here’s a rough backward schedule:

• Now – July 2024: Complete inventory of all JDK 22 instances. Evaluate upgrade paths (to an LTS release like JDK 17 or 21, or the next feature release). Start procurement for new licenses or support agreements.
• July – August 2024: Execute migration testing in staging and pre-production environments. Account for application compatibility, library dependencies, and performance regression tests.
• August – September 2024: Deploy the new JDK version to production. Allow a buffer for rollback if issues arise. Many organizations also face August/September change freezes, reducing deployment windows.

If your team hasn’t started a migration plan by now, hitting September 17 without a solution becomes a real risk.

Risks of Running Past the EOL Date Without Support

After September 17, 2024, Oracle will no longer provide security patches, bug fixes, or technical support for JDK 22. Running unsupported means:

• Exposure to unpatched vulnerabilities – New CVEs discovered after EOL will not be addressed by Oracle.
• Compliance gaps – Regulatory frameworks (e.g., PCI DSS, SOX) may require up-to-date software with active vendor support.
• No access to critical fixes – If a show-stopping bug surfaces, there will be no official path to resolution.

How Third-Party Support Removes the Deadline Pressure

Rather than rushing a migration, you can lock in third-party support for Oracle JDK 22 now. A provider like 3rd Party Support can deliver security patches and technical assistance for JDK 22 well past Oracle’s EOL date. This approach lets your team:

• Migrate on their own schedule – no forced upgrade before September 17.
• Extend the life of JDK 22 if applications are not yet ready for a newer release.
• Avoid emergency change windows and last-minute procurement.

By engaging third-party support before the EOL date, you eliminate the risk of running unsupported and regain control over your JDK roadmap.

Contact us to discuss how third-party support for Oracle JDK can fit your organization’s timeline.

Lifecycle source: endoflife.date/oracle-jdk