WildFly 41 Maintenance Plans

A number of users have requested that we produce additional WildFly 41 micro releases in order to address security vulnerabilities in libraries used in WildFly 41.

We do not plan to produce any further WildFly 41 releases. We certainly won’t be producing another WildFly 41 micro in the next couple of months.

WildFly’s general support lifecycle states that we will produce a single micro bug-fix release for each major, and will not produce further updates once the next major is released. The reason for this is producing a WildFly release, even a micro, requires a major investment of developer time and test infrastructure resources, and our developer community does not have the bandwidth to produce quality releases beyond what we say we will do in our support lifecycle statement.

The key driver for requests that I’ve seen for WildFly 41 updates is that 41 is the last release that supports EE 10. We’re aware that there can be some effort involved in updating an application to a later Jakarta EE version; this is why we produced the additional WildFly EE 10 variant for WildFly 40 and 41.

So, we’re sympathetic to the desire for further 41 updates, and we’ll keep an open mind about ways we may be helpful. But, honestly, I don’t anticipate we’ll be doing another 41 micro.

Note

As discussed in the WildFly and Java4Shell post, we do plan to update the WildFly 41.0.1 container images to incorporate versions of Java SE that patch the Java4Shell vulnerability.

Producing updates for the 41.0.1 images is outside our normal policies and is not something we expect to repeat.

If you are looking for a longer support lifecycle for an EE 10 server based on the WildFly technology stack, Red Hat’s JBoss Enterprise Application Platform is an option. Also, WildFly is a Commonhaus Foundation project, and the foundation sponsors the Commonhaus Foundation Open Source Sustainability Initiative (OSSI) to recognize organizations that take responsibility for the security and stability of open source software beyond its end-of-life. TuxCare is an OSSI Partner and provides support for older versions of WildFly.