Chris,
This strategy is working well, we have some statistics and controls that
are easier to implement and maintain if we keep separate connectors.
Currently, we have only two Tomcats, each one with 40 applications (focus
in justice, virtual processes) deployed on it and processing 160 req/sec.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Robert,
On 12/20/12 8:39 PM, Robert Anderson wrote:
> Now, the "trick": ... Include
> conf.d/mod_jk.mounts ...
>
> ... Include conf.d/mod_jk_sec.mounts ...
>
Oh, of course. It's still not necessary unless you have some other
kind of options t
Hi Chris,
It's a very good question. Yes, I'm using stick sessions.
-->server.xml (tomsrv01)
--> server.xml (tomsrv02)
-->worker.properties
worker.list=balancer,balancersec
worker.tomsrv01.type=ajp13
worker.tomsrv01.host=172.17.1.65
worker.tomsrv01.port=8009
worker
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Robert,
On 12/19/12 5:48 AM, Robert Anderson wrote:
> connectionTimeout="2" protocol="AJP/1.3" redirectPort="8443"
> /> scheme="https" enableLookups="false" connectionTimeout="2" />
>
> jvmRoute="*tomsrv02*">
>
> worker.properties
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bob,
On 12/18/12 8:48 PM, Bob Myers wrote:
> Some particular apps require HTTPS, so we use (in the web.xml for
> that webapp)
>
> confidential
>
> Then if the app is accessed by HTTP (Apache port 80), and is
> routed (AJP) to the insecure Tomcat
:
>
> On Dec 18, 2012, at 6:40 PM, Caldarale, Charles R wrote:
>
> >> From: Bob Myers
> >> Re: jvmRoute with multiple AJP Connectors for one Engine
> >
> >>>> >>>> protocol="AJP/1.3" redirectPort="443" /> >>&
On Dec 18, 2012, at 6:40 PM, Caldarale, Charles R wrote:
>> From: Bob Myers
>> Re: jvmRoute with multiple AJP Connectors for one Engine
>
>>>> >>> protocol="AJP/1.3" redirectPort="443" /> >>> executor="tomcatThr
> From: Bob Myers
> Re: jvmRoute with multiple AJP Connectors for one Engine
Don't top post - it's really annoying, and makes it extremely difficult to
follow the points of a conversation.
> > > > > protocol="AJP/1.3" redirectPort="443" />
Some particular apps require HTTPS, so we use (in the web.xml for that webapp)
confidential
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/HT
-BEGIN PGP SIGNED MESSAGE-
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:
>
> protocol="AJP/1.3" redirectPort="443" /> executor="tomcatThreadPool" port="8019" protocol="AJP/1.3"
> scheme=
I have more than one AJP connector for my Engine - one for HTTP, and one for
HTTPS:
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 -
11 matches
Mail list logo
