sidebar hamburger menu

WildFly®

WildFly is a registered trademark of the Commonhaus Foundation.


TuxCare's Endless Lifecycle Support (ELS) for WildFly provides security patches and selected bug fixes that are integral to the stable operation of applications running on these versions of WildFly. These components have either reached their end of standard support from vendors or have reached End of Life (EOL). Our ELS for WildFly service is designed to provide solutions for organizations that are not yet ready to migrate to newer versions and that are seeking long-term stability for their legacy WildFly applications.

This guide outlines the steps needed for WildFly server setup and configuration.

Supported Versions

  • WildFly 27.0.1.Final

Installation

Prerequisites

  • Java Development Kit (JDK) 11 or later installed (verify with java -version)
  • JAVA_HOME set to your JDK installation directory
  • Nexus repository access credentials (username and password) — contact sales@tuxcare.com
  • To browse available artifacts, visit TuxCare Nexus and click Sign in in the top right corner. You may need to refresh the page after logging in.

Linux Installation

  1. Download the TuxCare build

    Download from TuxCare using your credentials. For example, WildFly 27.0.1.Final:

    curl -u USERNAME:PASSWORD -O https://nexus.repo.tuxcare.com/repository/els_java/org/wildfly/wildfly-ee-dist/27.0.1.Final-tuxcare.1/wildfly-ee-dist-27.0.1.Final-tuxcare.1.tar.gz
    

    Replace USERNAME and PASSWORD with your TuxCare credentials (see Prerequisites above).

  2. Extract the archive

    Create an installation directory in your home folder and extract the archive into it:

    mkdir -p ~/wildfly
    tar -xzf wildfly-ee-dist-27.0.1.Final-tuxcare.1.tar.gz -C ~/wildfly --strip-components=1
    
  3. Verify the installation

    ~/wildfly/bin/standalone.sh --version
    

    The output should display the WildFly version and build details.

  4. Start WildFly

    ~/wildfly/bin/standalone.sh
    

    This command runs in the foreground and keeps the terminal busy. Use a second terminal to verify and stop the server.

  5. Verify the server is running

    • Go to http://localhost:8080/. You should see the default WildFly welcome page.

    • Or check from the terminal (successful output is HTML from WildFly):

      curl http://localhost:8080
      
  6. Stop WildFly

    ~/wildfly/bin/jboss-cli.sh --connect command=:shutdown
    

Windows Installation

  1. Download WildFly

    Download the .zip archive from Nexus using your credentials, for example wildfly-ee-dist-27.0.1.Final-tuxcare.1.zip.

  2. Extract the archive

    Extract it to the installation directory, e.g., C:\WildFly. The archive contains a top-level folder, so this produces C:\WildFly\wildfly-27.0.1.Final-tuxcare.1 — that folder is your WildFly directory.

  3. Start WildFly

    Run C:\WildFly\wildfly-27.0.1.Final-tuxcare.1\bin\standalone.bat.

    This window stays open while the server runs. Use your browser (next step) to verify it, and a second window to stop it.

  4. Verify the server is running

    Go to http://localhost:8080/ in your browser. You should see the default WildFly welcome page.

  5. Stop WildFly

    Run C:\WildFly\wildfly-27.0.1.Final-tuxcare.1\bin\jboss-cli.bat --connect command=:shutdown from a second window.

Use Case: Production Setup Linux

  1. Create a wildfly group

    sudo groupadd wildfly
    
  2. Create a wildfly user

    Create a new user as a member of the wildfly group, with a home directory of /opt/wildfly and the login shell set to /bin/false:

    sudo useradd -s /bin/false -g wildfly -d /opt/wildfly wildfly
    
  3. Install into /opt/wildfly and set ownership

    sudo mkdir -p /opt/wildfly
    sudo tar -xzf wildfly-ee-dist-27.0.1.Final-tuxcare.1.tar.gz -C /opt/wildfly --strip-components=1
    sudo chown -R wildfly:wildfly /opt/wildfly
    
  4. Start WildFly as the wildfly user

    sudo -u wildfly JAVA_HOME=/path/to/your/jdk /opt/wildfly/bin/standalone.sh
    

    sudo does not pass your environment to the target user, so set JAVA_HOME explicitly (or configure it for the wildfly user). Otherwise the server fails with java: command not found.

    Stop it from a second terminal with /opt/wildfly/bin/jboss-cli.sh --connect command=:shutdown.

Logs Location

Check logs for detailed error information:

  • Linux:

    ~/wildfly/standalone/log/server.log
    

    (or /opt/wildfly/standalone/log/server.log if you installed under a dedicated user)

  • Windows:

    C:\WildFly\wildfly-27.0.1.Final-tuxcare.1\standalone\log\server.log
    

What's Next?