# Java 26 ships HTTP/3 support and broader ahead-of-time object caching > Java 26 reaches general availability with HTTP/3 in its client API, garbage-collector-neutral object caching, and several explicitly preview features. Canonical URL: https://www.devobs.io/news/news-java-26-general-availability/ By: Samira Haddad Published: 2026-09-06T11:58:54.643Z Updated: 2026-09-06T11:58:54.643Z Event date: 2026-03-17 Section: Languages Oracle announced Java 26's general availability on March 17. The [release overview](https://blogs.oracle.com/java/the-arrival-of-java-26) spans networking, runtime behavior, and language work, while clearly separating permanent additions from features still collecting feedback. ## Runtime and library changes The release adds HTTP/3 support to the HTTP Client API and enables ahead-of-time object caching with any garbage collector. It also introduces warnings for deep-reflection mutation of final fields. Primitive patterns, lazy constants, and structured concurrency remain preview features; the Vector API remains incubating. The engineering consequence is a mixed adoption surface. A runtime upgrade, an application using a new networking capability, and a module depending on preview syntax should each have their own acceptance criteria. Combining them into one migration makes it harder to identify which change caused an unexpected result. ## Look for hidden reflective behavior The final-field warnings offer a particularly useful investigation point. Exercise serialization, dependency construction, and other infrastructure paths in representative application runs. If a warning appears, record the responsible library and call path before deciding whether the application needs a configuration change or a dependency update. For the caching changes, choose a startup measurement that includes the application's real initialization work and intended garbage collector. A small demonstration that starts quickly is useful evidence about that demonstration, but does not establish a service's cold-start behavior. Teams exploring the preview APIs can isolate experiments in a branch or module with an explicit removal plan. That keeps feedback practical without turning an unfinished API shape into an accidental long-term dependency. Java 26 offers several independent changes to evaluate; there is no requirement to adopt all of them together. ## Source references -