WildFly hosting for Jakarta EE applications

WildFly, the successor to JBoss AS

WildFly is the open source application server from Red Hat, formerly called JBoss Application Server. It implements the Jakarta EE platform: servlets, JPA, CDI, EJB, JMS, JAX-RS and more. If your application needs more than a servlet container, or you were running JBoss, WildFly is the natural home.

What we set up

• The latest WildFly release, downloaded from the official project and checked against its published checksum.
• WildFly runs as a systemd service under its own user, bound to localhost.
• JVM options sized to your server, with metaspace limits so a leak cannot eat the machine.
• Nginx in front with free SSL, and proxy address forwarding enabled so your application sees the real client address.
• The default welcome page removed, so your application owns the root of the domain.
• deploy-app app.war installs a WAR or EAR as the root application.

Administration

The management console and CLI listen on localhost only. You reach them through an SSH tunnel, for example ssh -L 9990:127.0.0.1:9990 you@your-server, then open http://localhost:9990. Nothing management-related is exposed to the internet.

How much memory

A fresh WildFly instance uses roughly 500 to 700 MB before your application loads. Add your application, its caches and the database. For production we recommend at least 4 GB, and 8 GB if the database runs on the same server. See how much RAM a Java app needs.

JBoss and EAP applications

Applications built for JBoss AS 7 or EAP often run on current WildFly with changes to the descriptors and the move from javax to jakarta packages. Managed plans include help migrating one application.