Public Repository

Last pushed: 2 years ago
Short Description
Docker Image to run Wildfly in Standalone HA mode on AWS
Full Description

Running Wildfly Standalone HA with Apache Modcluster

As Amazon Web Services does not allow multicast communcation, I had to configure the JGroups in wildfly to use a Gossip Router to set up clustering.

<subsystem xmlns="urn:jboss:domain:jgroups:4.0">
<channels default="ee">
<channel name="ee" stack="tcpgossip"/>
<stack name="tcpgossip">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<protocol type="TCPGOSSIP">
<property name="initial_hosts">
<property name="num_initial_members">${docker.gossiprouter.count:1}</property>
<property name="timeout">${jboss.jgroups.tcpgossip.timeout:3000}</property>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>

Apache Modcluster

Docker Image for Apache Modcluster can be found in the following repo:


Start the Apache httpd + modcluster.

docker run --rm -it --name modcluster -e MODCLUSTER_NET="192.168. 172. 10." -e MODCLUSTER_PORT=80 -p 80:80 -p 23364:23364 karm/mod_cluster-master-dockerhub

Check modcluster is running

JGroups Gossip Router

Docker Image for JGroups Gossip Router can be found in the following repo:


Start the JGroups Gossip Router

docker run -p 12001:12001 jboss/jgroups-gossip

Dockerfile and Resources

Dockerfile and resources used to run the Jboss image can be found in the following location:

Run Wildfly in standalone

docker run --rm -it -h wildfly-1 --name wildfly-1 -e MODCLUSTER_HOST= -e GOSSIP_ROUTER_HOST= -e GOSSIP_ROUTER_PORT=12001 sleepingtalent/wildfly-standalone-ha:1.0.4

Docker Pull Command