Hello,
You may want to take a completely different approach.
1) If your session is lightweight (no really heavy objects) you could
store everything in cookies and go completely session and stateless.
This would solve most of the problems.
2) If 1. isn't applicable - persist the session to a distrib
Jeffrey Janner wrote:
George -
This is why I hate statistics. You can make them say anything.
I was thinking the same thing, remembering the recent financial troubles.
1/( (2 hours)/24(Hours day) * 1/(3*365))/2 (Data centers)
- customers don't work 24 hours a day, they usually work 8 hours a
See comments [Jeff] below:
-Original Message-
From: George Sexton [mailto:geor...@mhsoftware.com]
Sent: Wednesday, August 26, 2009 2:39 PM
To: 'Tomcat Users List'
Subject: RE: Multiple data centers and redundency?
> -Original Message-
> From: Jeffrey Janner [ma
> -Original Message-
> From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
> Sent: Wednesday, August 26, 2009 12:53 PM
> To: Tomcat Users List
> Subject: RE: Multiple data centers and redundency?
>
> George -
> This is why I hate statistics. You ca
mbers of
users)
-Original Message-
From: George Sexton [mailto:geor...@mhsoftware.com]
Sent: Wednesday, August 26, 2009 9:52 AM
To: 'Tomcat Users List'
Subject: RE: Multiple data centers and redundency?
> -Original Message-
> From: Andre-John Mas [mailto:aj...@sympatico.ca]
>
> -Original Message-
> From: Andre-John Mas [mailto:aj...@sympatico.ca]
> Sent: Tuesday, August 25, 2009 6:30 PM
> To: Tomcat Users List
> Subject: Multiple data centers and redundency?
>
> Hi,
>
> I have been asked to look into a solution that would inv
On 25-Aug-2009, at 20:52, Hassan Schroeder wrote:
On Tue, Aug 25, 2009 at 5:38 PM, Andre-John Mas
wrote:
... The architecture would involve
a DNS server perodically giving out a DNS address for one DNS
server and
then an address for the other.
Huh?
Teaches me to proof read. The DNS s
On Tue, Aug 25, 2009 at 5:38 PM, Andre-John Mas wrote:
> ... The architecture would involve
> a DNS server perodically giving out a DNS address for one DNS server and
> then an address for the other.
Huh?
> I see there is clustering available with Tomcat, but I don't see how this
> works across
Hi,
I have just been given some more information. The architecture would
involve a DNS server perodically giving out a DNS address for one DNS
server and then an address for the other. Each data centre would have
multiple hosts, each running multiple tomcats. The load balancer would
take
Hi,
I have been asked to look into a solution that would involve a few
different data centres each with their own set of load balanced Tomcat
servers. The requirement is for the users not to lose their session if
one data center goes down. I have never had to work on something this
large
10 matches
Mail list logo