Show Table of Contents
16.6. Apache mod_jk
16.6.1. About the Apache mod_jk HTTP Connector
Apache
mod_jk is a HTTP connector which is provided for customers who need it for compatibility purposes. Apache mod_jk provides load balancing, and is a part of the jboss-eap-native-webserver-connectors that is contained in JBoss Web Container. For supported platforms, see https://access.redhat.com/site/articles/111663. The mod_jk connector 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 HTTPD 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_cluster HTTP connector, an Apache proxy server does not know the status of deployments on servers or server groups, and cannot adapt where it sends its work accordingly.
Just like
mod_cluster, mod_jk communicates over the AJP 1.3 protocol.
Note
mod_cluster is a more advanced load balancer than mod_jk. mod_cluster provides all of the functionality of mod_jk plus many additional features. For more information about mod_cluster, see Section 16.5.1, “About the mod_cluster HTTP Connector”.
Next step: Configure the JBoss EAP 6 to participate in a mod_jk load balancing group
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.