JDK 26 Enters Release Candidate Phase with Native HTTP/3 Support and Primitive Patterns

Mark Reinhold, Chief Architect of the Java Platform Group at Oracle, declared JDK 26 Release Candidate 1 in early February 2026. The general availability release is targeted for March 17, 2026, bringing 10 JDK Enhancement Proposals (JEPs) to the Java platform.

HTTP/3 for the HTTP Client API

The headline feature is native HTTP/3 support in Java's standard HTTP Client API. Java has been conspicuously late to HTTP/3 compared to Go, Node.js, and Rust ecosystems, which have had HTTP/3 support in their standard or widely-used networking libraries for over a year. Bringing HTTP/3 — which runs over QUIC rather than TCP — to the Java standard library means that enterprise Java applications can adopt QUIC-based transport without adding third-party dependencies, reducing supply chain risk for security-sensitive deployments.

HTTP/3's practical benefits include reduced connection establishment latency (QUIC combines the TLS and transport handshakes into a single round trip), better performance on lossy networks (QUIC's stream multiplexing avoids TCP's head-of-line blocking), and improved connection migration when clients change network interfaces. For Java applications serving mobile clients or operating over unreliable networks, these improvements translate to measurable user experience gains.

Primitive Types in Patterns

JDK 26 extends Java's pattern matching to support primitive types in all pattern contexts. Previously, instanceof and switch patterns worked only with reference types. The expansion allows primitive types to participate in pattern matching, enabling more expressive and concise code when working with numeric values, boolean flags, and other primitives. This continues the modernization trajectory from Project Amber, which has been systematically adding pattern matching capabilities to Java over several releases.

Structured Concurrency

Structured concurrency reaches its sixth preview iteration in JDK 26, reflecting the Java platform team's characteristically cautious approach to API stabilization. Structured concurrency provides a programming model where concurrent tasks are treated as a unit — started together, completed or canceled together — rather than as independent threads that must be manually coordinated. The extended preview period allows the API to be refined based on real-world usage feedback before being finalized.

Other Changes

Garbage collection improvements bring the ahead-of-time cache to all GC implementations, including ZGC, which was previously excluded. JDBC 4.5 adds AutoCloseable to the Array, Blob, Clob, NClob, and SQLXML interfaces, allowing these resources to be used in try-with-resources blocks — a quality-of-life improvement that reduces resource leak risks in database code.