Return-Path: 
 <tomcat-user-return-85119-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org
Received: (qmail 75418 invoked from network); 28 Nov 2003 17:15:32 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 28 Nov 2003 17:15:32 -0000
Received: (qmail 97858 invoked by uid 500); 28 Nov 2003 17:15:07 -0000
Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org
Received: (qmail 97836 invoked by uid 500); 28 Nov 2003 17:15:06 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 97823 invoked from network); 28 Nov 2003 17:15:06 -0000
Received: from unknown (HELO mail.kingland.com) (63.224.189.41)
  by daedalus.apache.org with SMTP; 28 Nov 2003 17:15:06 -0000
Received: by mail.kingland.com with Internet Mail Service (5.5.2653.19)
	id <WQY20W1A>; Fri, 28 Nov 2003 11:12:32 -0600
Message-ID: <88A2C82DD1E1D411A5500050DAC4712901DDA8D8@mail.kingland.com>
From: "Karau, Joe" <Joe.Karau@Kingland.com>
To: "'tomcat-user@jakarta.apache.org'" <tomcat-user@jakarta.apache.org>
Subject: Connections Refused
Date: Fri, 28 Nov 2003 11:12:31 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

We have started loadtesting the current release of our application, which on
4.1.12 we were able to acheive over 200 concurrent users.  However, our
current version is running on 4.1.24 and has not been able to respond to
more than 100 users.

When we have between 80-100 users using the system, any browser that does
not yet have an active session instantly receives a "page can not be
displayed" error.  However, all existing sessions seem to be plugging away
at a perfectly reasonable pace, withour errors.  

The box has plenty of CPU and memory available to it, and with the heap set
at 1Gig we have plenty left in the heap to use.

We have the "maxProcessers" set at 250, and according to logs we have not
yet reached the max.  We are not specifying a session manager in the webapps
configuration, and from my understanding a default with no max sessions
should be used.

I've searched the web, and the archives and I can't find anything that seems
to help.

If anyone has any ideas and or thoughts, I would really appreciate it.
Thanks

Joseph Karau 
Kingland Systems 
joe.karau@kingland.com 
507-536-3629 
AIM: jkarau3629 


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