Show Table of Contents
19.6. Apache mod_jk
19.6.1. About the Apache mod_jk HTTP Connector
mod_jkis a HTTP connector which is provided for customers who need it for compatibility purposes. It provides load balancing, and is a part of the
jboss-eap-native-webserver-connectorsthat is contained in JBoss Web Container. For supported platforms, see https://access.redhat.com/site/articles/111663. The
mod_jkconnector is maintained by Apache, and its documentation is located at http://tomcat.apache.org/connectors-doc/.
JBoss EAP 6 can accept workloads from an Apache HTTP proxy server. The proxy server accepts client requests from the web front-end, and passes the work to participating JBoss EAP 6 servers. If sticky sessions are enabled, the same client request always goes to the same JBoss EAP 6 server, unless the server is unavailable.
Unlike the JBoss
mod_clusterHTTP connector, an Apache
mod_jkHTTP connector does not know the status of deployments on servers or server groups, and cannot adapt where it sends its work accordingly.
mod_jkcommunicates over the AJP 1.3 protocol.
mod_clusteris a more advanced load balancer than
mod_clusterprovides all of the functionality of
mod_jkand additional features. For more information about
mod_cluster, see Section 19.5.1, “About the
Next step: Configure a JBoss EAP 6 instance to participate in a mod_jk load balancing group