Installation guide
<Location $LOCATION>
SetHandler mod_cluster-manager
Order deny,allow
Deny from all
Allow from 127.0.0.1
</Location>
When accessing the $LOCATION defined in the Location element in your browser, you will see
something like the following. (In this case, $LOCATION was also defined as mod_cluster-
handler.)
Figure 6.1. mod_cluster Sta t us
Transferred corresponds to the POST data sent to the worker node. Connected corresponds to the
number of requests that had been processed when this status page was requested. Sessions
corresponds to the number of active sessions. T his field is not present when Maxsessionid is 0.
6.1.2. mod_proxy_cluster.so
The Proxy Balancer module, mod_proxy_clust er, handles the routing of requests to cluster nodes.
The Proxy Balancer selects the appropriate node to forward the request to, based on application
location in the cluster, current state of each of the cluster nodes, and the Session ID (if a request is part
of an established session).
LoadModule proxy_cluster_module modules/mod_proxy_cluster.so
You can also define the following related directives in the <VirtualHost> element to change load-
balancing behavior.
mod_proxy_cluste r dire ctive s
CreateBalance rs
Defines how load balancers are created in the Apache HT TP Server virtual hosts. T he following
values are valid in CreateBalancers :
0
Create load balancers in all virtual hosts defined in Apache HT TP Server. Remember
to configure the load balancers in the ProxyPass directive.
1
Do not create balancers. When using this value, you must also define the load
balancer name in the ProxyPass or ProxyPassMatch .
2
Create only the main server. T his is the default value for CreateBalancers .
UseAlias
Defines whether to check that the defined Alias corresponds to the ServerName . The
following values are valid for UseAlias :
0
Ignore Alias information from worker nodes. T his is the default value for UseAlias .
JBoss Enterprise Application Platform 5 HTTP Connectors Load Balancing Guide 25