Road, Chennai
Ph: +91 98417 10021
Fonenet: (India) 550 - 16814
Mirou, Antoine [EMAIL PROTECTED]
11/14/2006 08:09 PM
Please respond to Tomcat Users List
To: Tomcat Users List users@tomcat.apache.org
cc:
Subject:RE: session replication/tomcat 5.5
Hello
Am 13.11.2006 um 20:27 schrieb David O'Dell:
Is anyone using session replication in production?
Yes, at really big sites :-)
Is there an alternative to using multicasting?
No, but you can implement you own membership service.
In the doc
: mardi 14 novembre 2006 09:31
À : Tomcat Users List
Objet : Re: session replication/tomcat 5.5
Am 13.11.2006 um 20:27 schrieb David O'Dell:
Is anyone using session replication in production?
Yes, at really big sites :-)
Is there an alternative to using multicasting?
No, but you can implement
users@tomcat.apache.org
cc:
Subject:RE: session replication/tomcat 5.5
Hello,
Could you please give an example of really big sites ?
How do you organize your cluster (how many members/domains, ...) ?
Do you use Farm-deployer ?
Do you use session replication ?
How do you
From: Mark Hagger [mailto:[EMAIL PROTECTED]
Subject: Re: session replication/tomcat 5.5
99.99% gives you a whole 3153 mins per year, or 52 hours, or
1 hour per week of operation per year.
Your premise is well taken, but the math is a bit shaky. 99.99% uptime
per week equates to 1 minute
: mardi 14 novembre 2006 09:31
À : Tomcat Users List
Objet : Re: session replication/tomcat 5.5
Am 13.11.2006 um 20:27 schrieb David O'Dell:
Is anyone using session replication in production?
Yes, at really big sites :-)
Is there an alternative to using multicasting?
No, but you can
On Tuesday 14 November 2006 16:49, Caldarale, Charles R wrote:
Your premise is well taken, but the math is a bit shaky. 99.99% uptime
per week equates to 1 minute of downtime in that period, not one hour,
which emphasizes you point even more.
Ooops, how embarrassing, I calculated everything
: David O'Dell [mailto:[EMAIL PROTECTED]
Sent: Monday, November 13, 2006 2:27 PM
To: Tomcat Users List
Subject: session replication/tomcat 5.5
Is anyone using session replication in production?
Is there an alternative to using multicasting?
In the doc http://tomcat.apache.org/tomcat-5.5-doc/cluster
, November 13, 2006 2:27 PM
To: Tomcat Users List
Subject: session replication/tomcat 5.5
Is anyone using session replication in production?
Is there an alternative to using multicasting?
In the doc http://tomcat.apache.org/tomcat-5.5-doc/cluster-howto.html
It states This is an algorithm
with the vital MRTG graphs on display.
Tim
-Original Message-
From: David O'Dell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006 3:03 PM
To: Tomcat Users List
Subject: Re: session replication/tomcat 5.5
Good to hear that someone is using this.
I want to try this out in my
, 2006 4:29 PM
To: 'Tomcat Users List'
Subject: RE: session replication/tomcat 5.5
I forgot to mention that we peak at about 6000 sessions on the average day.
The all-time max for 2006 is 6810 sessions.
For monitoring, we do several things.
1) We use lambda probe
2) We use MRTG and some scripts
in the engineering
department visible to most of us with the vital MRTG graphs on display.
Tim
-Original Message-
From: David O'Dell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006 3:03 PM
To: Tomcat Users List
Subject: Re: session replication/tomcat 5.5
Good to hear
transforms the XML to HTML.
Regards,
Dan
-Original Message-
From: Tim Lucia [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006 4:29 PM
To: 'Tomcat Users List'
Subject: RE: session replication/tomcat 5.5
I forgot to mention that we peak at about 6000 sessions on the
average day
PERFECT! Thanks to you and Dan Baumann...
-Original Message-
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006 4:59 PM
To: Tomcat Users List
Subject: Re: session replication/tomcat 5.5
Have a look at:
http://yourserver:yourport/manager/jmxproxy?qry
Is anyone using session replication in production?
Is there an alternative to using multicasting?
In the doc http://tomcat.apache.org/tomcat-5.5-doc/cluster-howto.html
It states This is an algorithm that is only efficient when the clusters
are small.
I have 6 tomcat instances behind a load
15 matches
Mail list logo
