WildFly is the open source implementation of the Jakarta EE suite of services. It comprises a set of offerings for enterprise customers who are looking for preconfigured profiles of JBoss Enterprise Middleware components that have been tested and certified together to provide an integrated experience.
It’s easy-to-use server architecture and high flexibility makes WildFly the ideal choice for users just starting out with Jakarta EE and Microprofile API, as well as senior architects looking for a customizable middleware platform.
WildFly is free and open-source software, subject to the requirements of the GNU Lesser General Public License (LGPL), version 2.1.
The latest version of WildFly is: 33.0.2.Final – May 2026
Top resources available in this section:
What is WildFly application server?
What is the difference between JBoss EAP, WildFly and JBoss AS ?
Choosing the right JDK for WildFly
How to Start, Stop and Restart WildFly
How to configure WildFly to bind to a different IP
Find out the version of WildFly you are running
How to manage a WildFly Domain
Configuring JVM Settings in a WildFlyDomain
How to set and load Properties in WildFly
Reading properties from a configuration folder in WildFly
How to use environment variables in WildFly configuration
How to access WildFly Admin Console
How to manage WildFly remotely
Solving java.net.BindException: Address already in use: JVM_Bind
Cargo is a framework that allows you to manipulate Java EE containers in a standard way. It ships with a sets of Api, ant tasks and maven plugins that can let you execute administration and deployment tasks. Installing Cargo Cargo sources are available at http://cargo.codehaus.org/Downloads If you need binaries, we suggest you … Read more
A common issue for many developers is how to solve Classloader issues, which are usually masked by strange errors like ClassCastException. Let’s see a concrete example, how to solve this issue for Web applications. The Classloading problem boils down to the fact that you have added in your deployment unit (Ex. WAR file) some libraries which … Read more
By default JBoss 4 and JBoss 5 uses a flat class loading model that avoids the need to redundantly include classes in different layers. WAR files would only have the web contents and servlets, EJBs their interfaces, implementations and types, etc. From 4.0.2 JBoss has changed to the Servlet spec classloading model, i.e. it uses … Read more