Java Reference
In-Depth Information
This option is disabled in the bundled server by default. Be sure to uncomment the
ServerAdvertise
directive in its
httpd.conf
file.
Now, restart the Apache web server and the single application server nodes. If you have
correctly configured the mode cluster on the HTTP side, you will see that each WildFly
node will start receiving UDP multicast messages from
mod_cluster
.
Note
If you are running on a Windows machine, be sure to run your web server as an adminis-
trator.
If everything goes well, you can visit
http://127.0.0.1:6666/
mod_cluster_manager
to see the status of your load balancer and the interconnected
nodes. Be sure to not use Google Chrome for this because it considers the
6666
port as
an unsecure one (it is an IRC port by default). You should see the following information
on the simple webpage:
mod_cluster/1.2.6.Final
Auto Refresh show DUMP output show INFO output
Node michal-pc (ajp://localhost:8009):
Enable Contexts Disable ContextsBalancer:
mycluster,LBGroup: ,Flushpackets: Off,Flushwait:
10000,Ping: 10000000,Smax: 65,Ttl: 60000000,Status:
OK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: 100
If you don't have a running WildFly instance
now, be sure to start it with one of the
full-HA configuration files. Refresh Apache's configuration web page after the server is
up.
Clustering your web applications
Clustering web applications requires the least amount of effort to be put in by the deve-
loper. As we have just discussed, all you need to do to switch on clustering in a web ap-
plication is to add the following directive to the
web.xml
descriptor:
<web-app>
<distributable/>
</web-app>
