WildFly 42 Adds Virtual-Thread Support for Java
The latest application server release enhances concurrency while scheduling the phase-out of support for Java 17.
Updated on Oct. 31, 2026 in Software
Live Poll
Do you find it necessary to prioritize migrating your software environment to the latest Java versions?
The WildFly project has released version 42 of its Java application server, introducing virtual-thread support in Jakarta Concurrency resources. This update maintains Jakarta EE 11 compatibility while discontinuing the temporary WildFly EE 10 variant.
Why it matters
This release marks a transition period for enterprise Java development by integrating concurrency improvements while establishing a clear timeline for phasing out support for older Java versions.
WildFly 42 introduces installation-specific software bills of materials (SBOMs) and native virtual-thread support through Jakarta Concurrency. The server currently supports Java 17 and Java 21, but Java 17 support is slated for removal in future versions.
The players
WildFly
An open-source Java application server project that provides a runtime environment for enterprise Jakarta EE applications.
The details
Virtual threads — lightweight threads managed by the Java runtime rather than the operating system — allow applications to handle higher volumes of concurrent requests with lower memory overhead. By integrating these into Jakarta Concurrency resources, the server enables developers to optimize resource usage in high-throughput environments. The release also includes installation-specific SBOMs, which provide a comprehensive inventory of the components and dependencies present in a specific server configuration to assist with security tracking.
Timeline
October 22, 2026: WildFly 42 release date.
Spring 2027: Expected release of WildFly 44.
The Tech Race
WildFly 42 aligns its development roadmap with the latest Jakarta EE 11 standards to remain competitive with other enterprise application runtimes. This release continues the shift toward modern Java versions, positioning the project to eventually drop support for older LTS releases like Java 17.
Developers using WildFly 42 can now leverage virtual threads to improve application concurrency, provided they are running on compatible Java versions. Those currently dependent on Java 17 must begin planning a migration to Java 21, as future WildFly releases will enforce this higher minimum requirement.
The takeaway
WildFly 42 provides an immediate pathway to utilizing modern virtual-thread concurrency within enterprise Jakarta EE environments. Users should monitor the transition schedule for WildFly 43 to avoid compatibility issues once Java 17 support is officially discontinued.
What happens next
The project will finalize Java 17 support in WildFly 43 before mandating Java 21 in WildFly 44, which is scheduled for release in spring 2027.
Further reading
For more updates on development environments and runtimes, explore the Software section.
Source note: This article includes information reported by ADTmag.
Live Poll
Do you find it necessary to prioritize migrating your software environment to the latest Java versions?
