tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bob Myers <>
Subject Re: jvmRoute with multiple AJP Connectors for one Engine
Date Wed, 19 Dec 2012 01:48:02 GMT
Some particular apps require HTTPS, so we use (in the web.xml for that webapp)


Then if the app is accessed by HTTP (Apache port 80), and is routed (AJP) to the insecure
Tomcat app on 8009, it is redirected to port 443 (redirectPort=443) for HTTPS instead, and
Apache passes 443/HTTPS traffic to Tomcat port 8019. Tomcat handles this well with the Connectors
using redirectPort and the secure=true/scheme=https parameters.

What do you mean, why bother? 

Some apps need HTTPS, some don't. We can define which is which in the web.xml files, so our
content developers control that themselves.

On Dec 18, 2012, at 5:29 PM, Christopher Schultz wrote:

> Hash: SHA256
> Bob,
> On 12/18/12 7:08 PM, Bob Myers wrote:
>> I have more than one AJP connector for my Engine - one for HTTP, 
>> and one for HTTPS:
>> <Connector executor="tomcatThreadPool" port="8009" 
>> protocol="AJP/1.3" redirectPort="443" /> <Connector 
>> executor="tomcatThreadPool" port="8019" protocol="AJP/1.3" 
>> scheme="https" secure="true" />
> Why bother?
>> I had two workers, tomcat and tomcatssl, using the two different 
>> port numbers, one for Apache HTTP and one for HTTPS connections. 
>> They use a common Engine and Executor thread pool.
>> So far, so good - until I tried to put in a second Tomcat server 
>> with load balancing. The jvmRoute is supposed to match the worker 
>> name, but now I have 2 connectors for a single Engine! The 2 
>> workers can't have the same name, though they need to go to the 
>> same Engine.
>> It seems to me that something is wrong here - the jvmRoute needs to
>> be set on the connector, not on the Engine.
>> There seems to be no alternative to using 2 separate Engines and 
>> not just 2 Connectors, and that also means separate Services, and a
>> non-common Executor pool.
>> Is there any way around this? Why is the jvmRoute set on the Engine
>> instead of the Connector?
> - -chris
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: GPGTools -
> Comment: Using GnuPG with undefined -
> JAoAn04/IXEKbg0pfpoHD5XWhgNUUsmS
> =VsS+
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message