Clustering WildFly

This tutorial is about Load Balancing a cluster of WildFly servers using a WildFly front-end server configured using the load-balancer profile. Since WildFly 9, you can use an instance of the Application Server as a mod_cluster front-end for your back-end applications. This removes the need to use a native Web server like Apache (and mod_cluster … Read more

There are different options to change the default multicast address depending on the version of JBoss / WildFly which you are using. Changing the multicast address in WildFly In WildFly the System Property which controls the default multicast address is jboss.default.multicast.address and defaults to 230.0.0.4 <socket-binding name=”jgroups-udp” interface=”private” port=”55200″ multicast-address=”${jboss.default.multicast.address:230.0.0.4}” multicast-port=”45688″/> Therefore, you can change … Read more

Please note: This tutorial has been written for JBoss EAP 5/6 and early versions of WildFly. The current version of WildFly or JBoss EAP 7 no longer requires you to enable the clustering behavior. By default, if the server is started using the “ha” or “full-ha”, the state of SFSBs will be replicated automatically and … Read more

In this tutorial we will learn how to configure Load Balancing Groups with mod_cluster so that requests for your applications are not spread randomly across the full WildFly cluster. Application requests will be sent first to other nodes available in a given Balancing Group before it is sent to another Load Balancing Group. Our starting … Read more

The mod_cluster distribution includes a manager application which can be used to test your cluster topology and manage as well deployed applications across the cluster. In this tutorial we will show how to protect access to the mod_cluster_manager application with a password. In order to protect our mod_cluster_manager application we will use a standard Apache … Read more

This tutorial discusses in detail how to configure HTTP Session Management in clustered Web applications, based on the new changes introduced in WildFly 17. Web applications which are running in a cluster-aware configuration (“ha” or “full-ha” profile) can survive the lifespan of a single server by adding the element into the web.xml file. Example: <web-app … Read more

One of the new features included in WildFly 18 is the ability to load balance requests using a ranked order of preference. The default session affinity algorithm in a WilFly cluster is set by the “affinity” attribute: /subsystem=undertow/configuration=filter/mod-cluster=load-balancer:read-resource() { “outcome” => “success”, “result” => { “advertise-frequency” => 10000, . . . . “affinity” => {“single” … Read more

High Availability in WildFly serves the purpose to guarantee the availability of Java EE application. As the number of request for an application increase, there are two potential issues: Failure of the application, if the only node where it runs crashes. Delays in serving requests, if the server is unable to handle the load. In … Read more

JBoss farming service was available for early versions of the application server. such as JBoss 4 and JBoss 5. This tutorial discusses how to configure it and which are the alternatives available for new versions of the application server. What is JBoss Farming Service? The farming service is an hot-deploy feature available in the “all” … Read more

Mod cluster is an http based load balancer which greatly simplify the setup of an http cluster. It ships as a set of modules which need to be installed on the httpd server and a Service Archive Library (.sar) which needs to be deployed on WildFly. Wildfly is also able to handle front-end requests with … Read more