Skip to content
This repository

mod_cluster is an intelligent Apache httpd-based load-balancer

README.md

mod_cluster

Project mod_cluster is a httpd-based load-balancer. It uses a communication channel to forward requests from httpd to one of a set of application server nodes. Unlike mod_jk and mod_proxy, mod_cluster leverages an additional connection between the application server nodes and httpd to transmit server-side load-balance factors and lifecycle events back to httpd. This additional feedback channel allows mod_cluster to offer a level of intelligence and granularity not found in other load-balancing solutions.

Mod_cluster boasts the following advantages over other httpd-based load-balancers:

  • Dynamic configuration of httpd workers
  • Server-side load balance factor calculation
  • Fine grained web-app lifecycle control
  • AJP is optional

http://www.jboss.org/mod_cluster

Installation

JBoss AS 7/WildFly 8+

These versions already ship with bundled mod_cluster. It is configured via mod_cluster subsystem.

JBoss AS 6

This is the first version of AS that bundled mod_cluster, the configuration is located in /server/<profile>/deploy/mod_cluster.sar/META-INF directory.

JBoss AS 5/6

  1. Copy the exploded sar mod_cluster.sar directory into the deploy directory of a JBoss AS server profile.
  2. Modify the server.xml within jbossweb.sar and add a clustered mode engine listener as documented here.

JBoss Web / Tomcat

The tar.gz from the assembly contains the JBossWeb-Tomcat.

  1. Extract the JBossWeb-Tomcat directory.
  2. Copy the JAR files from JBossWeb-Tomcat/lib to the Tomcat lib.
  3. Remove the mod_cluster-container-tomcat(n).jar that does correspond to the Tomcat version you are using.
  4. Copy the JBossWeb-Tomcat/lib/jboss-logging-jdk.jar and JBossWeb-Tomcat/lib/jboss-logging-spi.jar dependency jars into the same lib directory.
  5. Modify server.xml within the conf directory and add a non-cluster mode engine listener as documented here.

Project Structure

container-spi (contains no dependencies on a specific web container)
container
  catalina (base Tomcat/JBoss Web container implementation, based on Tomcat 5.5)
  catalina-standalone (contains ModClusterListener, used for standalone Tomcat/JBoss Web installations)
  jbossweb (JBoss Web container implementation, all versions)
  tomcat6 (Tomcat 6.0 container implementation)
  tomcat7 (Tomcat 7.0 container implementation)
core
demo
  client
  server
native (native httpd modules)

Building

Servlet Container Modules

Before building, ensure you have Maven version 3.0 or newer (mvn -version) and JDK 6.0 or newer (java -version). It is possible to build modules for all containers:

mvn install

Distribution package:

mvn -P dist package

Dynamic load-balancing demo is located in the /demo directory:

mvn install

Reverse Proxy (httpd) Modules

To build the native component from the sources you need a C compiler and the following tools:

  • m4
  • perl
  • autoconf
  • automake
  • libtool
  • make
  • patch
  • python

Of course the make and the patch must be GNU ones. For example on Solaris you need:

  • SMCm4 (requires libsigsegv and libgcc34)
  • SMCperl
  • SMCautoc
  • SMCautom
  • SMClibt
  • SMCmake
  • SMCpatch
  • SMCpython

All can be downloaded from http://www.sunfreeware.com/.

License

This software is distributed under the terms of the FSF Lesser Gnu Public License (see lgpl.txt).

Something went wrong with that request. Please try again.