Java Reference
In-Depth Information
starts up necessary parts of the application server container needed by the loaded applica-
tions.
If you need to customize the start-up properties of your application server, open the
standalone.conf
file (or
standalone.conf.bat
for Windows users), where the
memory requirements of Wildfly have been declared. Here is the Linux core section of
this file:
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m
-Djava.net.preferIPv4Stack=true"
JAVA_OPTS="$JAVA_OPTS
-Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS
-Djava.awt.headless=true"
else
echo "JAVA_OPTS already set in environment; overriding
default settings with values: $JAVA_OPTS"
So, by default, the application server starts with a minimum memory requirement of 64
MB of heap space and a maximum of 512 MB. This will be just enough to get started;
however, if you need to run more robust Java EE applications on it, you will likely require
at least 1 GB of heap space or 2 GB or more, depending on your application type. Gener-
ally speaking, 32-bit machines cannot execute a process whose space exceeds 2 GB;
however, on 64-bit machines, there is essentially no limit to the process size.
You can verify that the server is reachable from the network by simply pointing your
browser to the application server's welcome page, which can be accessed from the well-
known address,
http://localhost:8080
. The welcome page of WildFly is shown
in the following screenshot:
