A detailed analysis of Apache+tomcat load Balancing Setup method

First, Introduction:

Each tomcat worker is a tomcat instance that serves the Web server and waits for the servlet to execute. For example, we often use Web servers like Apache to forward Sevlet requests to a Tomcat process that is located behind it (that is, the worker mentioned earlier). This article describes in detail how to configure various types of worker and loadbalance, and explains the characteristics of various types of worker and the rationale for LoadBalance configuration.

Second, why use Tomcat workers:

Described above is a very simple structure that can in fact configure multiple Tomcat workers to handle the servlet requests forwarded by the Web server. The reasons for this configuration are the following hypothetical environments:

* We publish different Tomcat workers for their different applications in the development environment. Of course the developers in the development environment share the same Web server, but each Tomcat Worke serves the developer who owns it.

* We define our own virtual hosts on different Tomcat processes so that different companies can use their own web site so that their web site is split up reasonably.

* We provide a load-balanced web site, which means that multiple Tomcat workers are used simultaneously, and each tomcat worker has a separate host and assigns requests forwarded over the Web server between workers.

Of course, these scenarios may not cover all the situations where multiple workers are used.

Three, workers.properties configuration description:

The way to define tomcat workers is to write a property file named "Workers.properties" under the Apache Conf directory. This article will explain in detail how to configure:

1. Define Workers list:

The way to define workers is to write a workers.properties file in Apache's conf directory, making it work as an Apache plug-in.

To define the format of the workers list:

Worker.list =< Use the "," split list of worker names >