How to start/stop the WildFly server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2
How to access at WildFly server console? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
How is Apache server connected with WildFly? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
How to change the Java memory settings for WildFly? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
How to debug errors?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
WildFly
1
Bitnami WildFly Stack bundles WildFly Application Server. If you are using Bitnami JBoss please check this
documentation.
How to start/stop the WildFly server?
If you deployed WildFly using the Bitnami native installers you can use the Manager Graphical tool.
For the the virtual machines and cloud images you can use the "ctlscript.sh" utility which is in the
installation directory (/opt/bitnami).
$ ./ctlscript.sh start wildfly
How to access at WildFly server console?
For security reasons, the WildFly server console will be accessible only when using 127.0.0.1 as the
hostname. If you are using a native installer you can access from your own machine but if you are using a
Virtual Machine, Amazon cloud image or Windows Azure cloud image, please check the connection steps
below.
Amazon cloud / BitNami Hosting
By default WildFly Management Console is not accessible from the outside for security reasons. In order to
access it, you can create an SSH tunnel to WildFly Management Console, sending your requests to your
webserver from 127.0.0.1 (localhost).
1. Get your SSH private key if you don't have it already. More info
2. Create the tunnel.
- If you are in Linux or Mac you can run the following in a Terminal in your local machine (using your
Public DNS instead of xyz.bitnamiapp.com):
ssh -N -L 9992:127.0.0.1:9990 -i bitnami-hosting.pem
bitnami@xyz.bitnamiapp.com
- If you are using Windows, you can use Putty:
Follow the steps described here
Before opening the connection. Go to Connection -> SSH -> Tunnels, enter the values below and
click "Add" button:
? Source port: "9992"
? Destination: "localhost:9990"
Click Open
3. While the tunnel is active you can connect to the web console at http://127.0.0.1:9992/console in your
browser. The default login is:
username/login: manager
password: <user defined> (default: auto-generated more info)
WildFly
2
Take a look at this link about how to get your application password for BCH servers
Native Installer
To test your WildFly installation, first make sure that your Apache and WildFly servers are up and running.
To do so, you can use the included "ctlscript.sh" utility. The installdir for Virtual Appliances and AMIs is
"/opt/bitnami".
cd your_installdir
./ctlscript.sh status
If you need to start or stop the servers, you just have to follow the steps described here.
You can access your WildFly Management Console by opening a browser and typing http://127.0.0.1:8080/
console or http://127.0.0.1/console.
The default root user is manager and the password is the same you set during the installation.
In case you want to access WildFly Management Console from another machine, you have to do two
modifications.
1. Modify the installation_directory/wildfly/conf/wildfly.conf file to add the following line.
<Location />
ProxyPreserveHost On
ProxyPass http://localhost:8090/
</Location>
2. Modify the WildFly standalone configuration file, installation_directory/wildfly/standalone/
configuration/standalone.xml, to allow access to the Management interface to other hosts.
...
<interface name="management">
<inet-address value="${jboss.bind.address.management:0.0.0.0}"/>
</interface>
...
Finally, restart your servers to load the new configuration
cd your_installdir
./ctlscript.sh restart
Virtual Machine
If you are running the Virtual Appliance in a secure environment, you can enable the management console
by editing the "/opt/bitnami/wildfly/conf/wildfly.conf" file and adding the following line in the <Location>
directive
WildFly
3
<Location />
ProxyPreserveHost On
ProxyPass http://localhost:8080/
</Location>
Moreover, you have to modify the WildFly standalone configuration file, installation_directory/wildfly/
standalone/configuration/standalone.xml, to allow access to the Management interface to other hosts.
...
<interface name="management">
<inet-address value="${jboss.bind.address.management:0.0.0.0}"/>
</interface>
...
After that, allow the access to the Management Console port (9990) through the firewall.
sudo ufw allow 9990
Finally, restart your servers to load the new configurations:
$ cd /opt/bitnami
$ sudo ./ctlscript.sh restart
Then you can access at the same URL with "/console", for example http://YOUR_IP/console
The default root user is manager. For Virtual Appliances the password is bitnami
Azure cloud
By default WildFly Management Console is not accessible from the outside for security reasons. In order to
access it, you can create an SSH tunnel to WildFly Console, sending your requests to your webserver from
127.0.0.1 (localhost).
You should follow these steps to create the tunnel:
1. Create the tunnel.
- If you are in Linux or Mac you can run the following in a Terminal in your local machine (using your
Public DNS instead of xyz.bitnamiapp.com):
$ ssh -N -L 9992:127.0.0.1:9990 your_azure_user@xxx.cloudapp.com
- If you are using Windows, you can use Putty:
Follow the steps described here
Before opening the connection. Go to Connection -> SSH -> Tunnels, enter the values below and
click "Add" button:
? Source port: "9992"
? Destination: "localhost:9990"
WildFly
4
Click Open
2. While the tunnel is active you can connect to the WildFly Management Console through
http://127.0.0.1:9992:consolein your browser. The default login is:
username/login: manager
password: <user defined> (default: auto-generated more info)
Tabs end
How is Apache server connected with WildFly?
Bitnami Stacks ship Apache server. There are different ways to connect these two servers. One of this is
connecting through HTTP proxy.
The HTTP Connector element represents a Connector component that communicates with a web
connector via the HTTP protocol. This is used for cases where you wish to invisibly integrate WildFly into
an Apache installation, and you want Apache to handle the static content contained in the web application,
and/or utilize Apache's SSL processing.
To make them work together, we enable the "mod_proxy.so" and "mod_proxy_http.so" modules in
"installdir/apache2/conf/httpd.conf" and add the following lines in the "installdir/wildfly/conf/
wildfly.conf file:
<Location /your_application_url>
ProxyPass http://localhost:8090/your_application_url
</Location>
In Bitnami WildFly Stack WildFly HTTP listensat port 8090 and in Bitnami Cloud Hosting it listens at
port 8083 by default and a connector is configured to make the application accessible at
http://localhost:PORT and http://xyz.bitnamiapp.com/wildfly/ respectively.
How to change the Java memory settings for WildFly?
If you find an error similar to this, the problem is that you need to increase the Java memory settings for
WildFly.
java.lang.OutOfMemoryError: PermGen space
You can find below the steps to increase Java settings on your side:
On Windows: Edit the /installdir/wildfly/scripts/setenv.bat file and increase the Java settings. For
example:
SET JAVA_OPTS="%JAVA_OPTS% -XX:MaxPermSize=1024m -Xmx1024m"
Then it is necessary to uninstall and install the service again. Open a command prompt as administrator
and run the following commands:
WildFly
5
> cd installdir
> serviceinstall.bat UNINSTALL (this command will close your current
window)
> serviceinstall.bat INSTALL
How to debug errors?
The main WildFly log file is created at /installdir/wildfly/standalone/log/wildfly.out.
WildFly
6