Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
From: "Filip Hanik \(lists\)" <devlists@hanik.com>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Subject: RE: tomcat 5.0.19 cluster problem
Date: Mon, 23 Feb 2004 11:39:44 -0800
Message-ID: <CIEPIAPFGBKPEBHPGDJJIEHOFIAA.devlists@hanik.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 8bit
In-Reply-To: <403A556E.8030501@terra.es>
Importance: Normal

yes, three servers in a cluster means three times the amount of memory used
for session data.
checking your -Xmx setting might be a good thing

-----Original Message-----
From: Antonio Fiol Bonn�n [mailto:fiol.bonnin@terra.es]
Sent: Monday, February 23, 2004 11:33 AM
To: Tomcat Users List
Subject: Re: tomcat 5.0.19 cluster problem


Filip Hanik (lists) wrote:

>>In any case could a cluster node that ran out of memory destroy the
>>entire cluster?
>>
>>
>
>it shouldn't, it can temporary slow it down if the node that is down is
>accepting connections and broad casting its membership.
>I'm running a load test right now with the latest version to make sure that
>I am not BS:ing you here :)
>
>Filip
>
>
>

Hi,

If you use in-memory replication, and the source of your
OutOfMemoryError is that you have too many objects stored in sessions,
or those objects are too big, or whatever, I think this could bring down
your entire cluster. What do you think, Filip?


Antonio

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.585 / Virus Database: 370 - Release Date: 2/11/2004


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org