Use the mod_cluster demo application
Basic Usage To run the demo application: Unpack the mod_cluster distribution on your filesystem. Here we assume it has been unzipped to ~/mod_cluster or C:\mod_cluster. Install mod_cluster into your httpd server as described at Installation of the httpd part Install mod_cluster into your JBossAS/JBossWeb/Tomcat servers as described at Installation on the Java side Start httpd and your JBossAS/JBossWeb/Tomcat servers Deploy the load-demo.war found in the distribution's demo/server folder to your JBossAS/JBossWeb/Tomcat servers. Start the demo application: On *nix: cd ~/mod_cluster/demo/client ./run-demo.sh On Windows: C:\>cd mod_cluster\demo\client C:\mod_cluster\demo\client>run-demo Configure the hostname and address of the httpd server, the number of client threads, etc and click the "Start" button. See Client Driver Configuration Options for details on the configuration options. Switch to the "Request Balancing" tab to see how many requests are going to each of your JBossAS/JBossWeb/Tomcat servers. Switch to the "Session Balancing" tab to see how many active sessions [2] are being hosted by each of your JBossAS/JBossWeb/Tomcat servers. Stop some of your JBossAS/JBossWeb/Tomcat servers and/or undeploy the load-demo.war from some of the servers and see the effect this has on load balancing. Restart some of your JBossAS/JBossWeb/Tomcat servers and/or re-deploy the load-demo.war to some of the servers and see the effect this has on load balancing. Experiment with adding artificial load to one or more servers to see what effect that has on load balancing. See Load Generation Scenarios for details. Most of the various panels in application interface also present information on the current status on any client threads. "Total Clients" is the number of client threads created since the last time the "Start" button was pushed. "Live Clients" is the number of threads currently running. "Failed Clients" is the number of clients that terminated abnormally; i.e. made a request that resulted in something other than an HTTP 200 response.