Return-Path: 
 <users-return-208039-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 18919 invoked from network); 8 Feb 2010 11:57:08 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 8 Feb 2010 11:57:08 -0000
Received: (qmail 76666 invoked by uid 500); 8 Feb 2010 11:57:04 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 76577 invoked by uid 500); 8 Feb 2010 11:57:04 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 76566 invoked by uid 99); 8 Feb 2010 11:57:04 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Feb 2010 11:57:04 +0000
X-ASF-Spam-Status: No, hits=0.7 required=10.0
	tests=SPF_SOFTFAIL
X-Spam-Check-By: apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 pid@pidster.com does not designate 209.85.212.45 as permitted sender)
Received: from [209.85.212.45] (HELO mail-vw0-f45.google.com) (209.85.212.45)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Feb 2010 11:56:52 +0000
Received: by vws7 with SMTP id 7so657077vws.18
        for <users@tomcat.apache.org>; Mon, 08 Feb 2010 03:56:29 -0800 (PST)
Received: by 10.220.125.10 with SMTP id w10mr8405419vcr.42.1265630188240;
        Mon, 08 Feb 2010 03:56:28 -0800 (PST)
Received: from phoenix.config (94-193-98-41.zone7.bethere.co.uk
 [94.193.98.41])
        by mx.google.com with ESMTPS id 28sm43387545vws.1.2010.02.08.03.56.26
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Mon, 08 Feb 2010 03:56:27 -0800 (PST)
Message-ID: <4B6FFBE7.4010808@pidster.com>
Date: Mon, 08 Feb 2010 11:56:23 +0000
From: Pid <pid@pidster.com>
Reply-To: pid@pidster.com
Organization: Pidster Inc
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: More than 20 users not able to access the application...
References: <31625062.384551265611026774.JavaMail.nabble@isper.nabble.com>
In-Reply-To: <31625062.384551265611026774.JavaMail.nabble@isper.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

On 08/02/2010 06:37, munirathinavel@gmail.com wrote:
> I'm having the following configuration.....

Please reply to the list only.

Leaving the whole/majority of the previous message intact helps other 
readers follow the thread.

Again, no need for all the extra spacing.


>         OS- Windows Server 2008
>         RAM- 4 GB
>         Processor-Intel Xeon(R)
>
>         Tomcat version-6.0.18
>
>             >This is my server.xml configuration......
>
>                                     <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
>                                    maxThreads="400" minSpareThreads="4" maxSpareThreads="100" />

What, all of it?

>         JVM memory settings:
>         Path -C:\Program Files\Java\jdk1.6.0_16\jre\bin\server\jvm.dll
>         Initial memory pool        - 1024 MB
>         Maximum memory pool   - 2560 MB
>         Thread stack size         - 1024 KB

I'm not a Windows expert, but that doesn't look

>            Last few days I'm doing load testing in my application.Two days back i did a load testing with 20 concurrent users and the application responding very slowly.Some pages are not getting loaded. In Mozilla (Firebug) I'm getting Page Aborted as the status.
>
>             Can you please tell me what is the problem and how can i proceed with more than 20 concurrent users.
>
>                                                                     Thanks.

Based on the information you've provided I'd have to guess that your 
application is the problem.  You can proceed with more than 20 
concurrent users by fixing your application.

Tomcat is known to support very high loads in production, some regulars 
on the list here will attest to that.


Read the following:
  http://catb.org/~esr/faqs/smart-questions.html

What does your application do?

How are you load testing your application, exactly?

What do your application logs say during the slow down?


p

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