From ef32aea21b90e912b517a0d97f20fa1b220ad343 Mon Sep 17 00:00:00 2001 From: Radoslav Husar Date: Wed, 7 Nov 2018 15:39:57 +0100 Subject: [PATCH] MODCLUSTER-638 Mod_cluster listener doesn't start: misleading docs --- docs/src/main/asciidoc/container-integration.adoc | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/docs/src/main/asciidoc/container-integration.adoc b/docs/src/main/asciidoc/container-integration.adoc index 7de6b7cb..82779fb6 100644 --- a/docs/src/main/asciidoc/container-integration.adoc +++ b/docs/src/main/asciidoc/container-integration.adoc @@ -55,11 +55,21 @@ e.g. ---- -=== Connectors +=== Tomcat connector Like mod_jk and mod_proxy_balancer, mod_cluster requires a connector in your server.xml to which to forward web requests. Unlike mod_jk and mod_proxy_balancer, mod_cluster is not confined to AJP, but can use HTTP as well. While AJP is generally -faster, an HTTP connector can optionally be secured via SSL. If multiple possible connectors are defined in your server.xml, +faster, an HTTP connector can optionally be secured via SSL. + +Since mod_cluster 1.4, the connector registered with the balancer is no longer automatically chosen by mod_cluster and needs to be specified explicitly. +The new attributes `connectorPort` and/or `connectorAddress` need to be configured explicitly matching exactly one of the configured connectors, e.g.: + +[source,xml] +---- + +---- + +In mod_cluster version 1.3 and older, if multiple possible connectors are defined in your server.xml, mod_cluster uses the following algorithm to choose between them: . If an native (APR) AJP connector is available, use it.