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
In this short tutorial we will learn which are the basic requirements to run WildFly application server. The basic requirements to start WildFly are: A JDK available on your machine The right amount of memory settings for the JDK. Let’s see both requirements. Download the appropriate JDK for your WildFly version Each recent WildFly version … Read more
If your WildFly server is unable to accept remote connections then keep reading this tutorial, we will help you to solve the issue. For security reasons, WildFly application server uses for its public and management interfaces, as fallback the loopback address: <interfaces> <interface name=”management”> <inet-address value=”${jboss.bind.address.management:127.0.0.1}”/> </interface> <interface name=”public”> <inet-address value=”${jboss.bind.address:127.0.0.1}”/> </interface> </interfaces> This means, … Read more
Do you have issues when starting WildFly ? This tutorial will teach you how to troubleshooting issues when WildFly fails to start. Let’s see some possible causes of failure in starting WildFly Application Server: Port already in use: This is one of the most common issues that could happen if you are starting WildFly on … Read more
WildFly HOME Directory is determined by the variable JBOSS_HOME. Therefore, in order to set it on a Linux Machine you need to: $ export JBOSS_HOME=/home/francesco/jboss/wildfly-17.0.0.Final For Microsoft Windows, from the Windows Start Menu, select Settings, select Control Panel, select System, select Advanced, then select Environment Variables. Click New. In the Variable Name field, enter JBOSS_HOME. … Read more
This tutorial shows how you can shutdown WildFly gracefully. WildFly can be suspended or shut down gracefully. This allows permits running requests to complete normally, without accepting new requests. Moreover, you can specify a timeout to define how long the suspend or shut down operation will wait for active requests to complete. You can shutdown … Read more
The easiest way is to install WildFly on Mac OS X is through Homebrew the free open-source package managment system. Requirements: install homebrew first. ruby -e “$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)” < /dev/null 2> /dev/null Then, install WildFly as follows: $ brew update Already up-to-date. $ brew search wildfly wildfly-as $ brew install wildfly-as ==> Downloading https://download.jboss.org/wildfly/16.0.0.Final/wildfly-16.0.0.Final.tar.gz … Read more
In this tutorial we to solve the issue “jboss.network.management: failed to resolve interface management“ This issue can be verified if you try to assign an IP address to a standalone server. For example: $./standalone.sh -b=192.168.10.1 -bmanagement=192.168.10.1 However we get the following error: ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC00001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException … Read more
In this tutorial we will learn the basic folder structure of WildFly application server. Let’s begin from the root folder: appclient: Configuration files, deployment content, and writable areas used by the application client container are run from this installation. bin: Contains startup scripts and also scripts for installing WildFly as a service and libraries for … Read more
This tutorial discusses how to set WildFly bind address using command line arguments and the configuration file. It applies to all WildFly versions and JBoss EAP as well. WildFly application server and JBoss EAP include two network interfces . There are two interfaces: “public” and “management”: <interfaces> <interface name=”management”> <inet-address value=”${jboss.bind.address.management:127.0.0.1}”/> </interface> <interface name=”public”> <inet-address … Read more
In WildFly expressions are mechanism that enables you to support variables in your attributes. A typical usage is that you want the value of attribute to be resolved using System or Environment properties. An example expression is: ${jboss.bind.address.management:127.0.0.1} This means that the value should derive from a system property named jboss.bind.address.management and if it is … Read more