Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Message-ID: <01b601c47adc$f0cfcac0$b2e8fc3e@EstafetLaptop>
From: "Michael Watson" <michael.watson@estafet.com>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
References: <cesj45$8rm$1@sea.gmane.org> <4111F1C1.7060508@apache.org>
Subject: Session Management Question
Date: Thu, 5 Aug 2004 12:11:20 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hi All,

This may have been answered elsewhere in the past but I'm struggling to find
it if it has - though please point me in the direction of past answers if
that's the case.

I'm trying to understand how a single instance of Tomcat manages sessions.
Is there any pooling/recycling of sesssion objects or are they
created/destroyed as required?
If they are pooled, is the size of this pool configurable?

Also where can I find some good documentation on managing sessions across a
cluster or load balanced instances?

Does anyone know of a practical limit for the number of concurrent
connections Tomcat can cope with on a reasonably out of the box Redhat
installation (obviously file descriptor limits aside)?

I realise this is more of a user question, but I figure members of this list
are more likely to be able to provide me with the level of detail I'm
looking for.

Any info you can supply would be much appreciated (I also need to find this
out with some urgency)

Thanks in advance

Mike


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.709 / Virus Database: 465 - Release Date: 22/06/2004


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