-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin,
On 5/11/2009 11:47 AM, Robin Wilson wrote:
> Actually,
Actually,
> From: Nenad Kovacevic [mailto:micami...@yahoo.com]
> Subject: RE: Getting the Right High Availability Architecture for
> Tomcat
>
> Our applications do not issue concurrent requests to the servers, i.e.
> they are classical web applications where the user activates a contr
e are running Tomcat 6.0.18 on SunOS 5.8, our
current java is 1.5 update 11.
--
View this message in context:
http://www.nabble.com/Getting-the-Right-High-Availability-Architecture-for-Tomcat-tp23452018p23485700.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---
Nenad Kovacevic wrote:
Caldarale, Charles R wrote:
Have you considered doing the SSL processing in the load balancer(s)? It
would make life simpler.
- Chuck
From application's perspective it really does not make much of a difference
where SSL is done - actually it does make now after
I am not sure if that is really an issue
or not?
Thanks
Nash
--
View this message in context:
http://www.nabble.com/Getting-the-Right-High-Availability-Architecture-for-Tomcat-tp23452018p23485311.html
Sent from the Tomcat - User ma
> From: Nenad Kovacevic [mailto:micami...@yahoo.com]
> Subject: Getting the Right High Availability Architecture for Tomcat
>
> If the session is replicated across the cluster should it not be
> irrelevant where a request gets processed?
The problem is that multiple requests as
ash
--
View this message in context:
http://www.nabble.com/Getting-the-Right-High-Availability-Architecture-for-Tomcat-tp23452018p23452018.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
