Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 31678 invoked from network); 8 Apr 2010 03:56:51 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Apr 2010 03:56:51 -0000 Received: (qmail 28583 invoked by uid 500); 8 Apr 2010 03:56:48 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 28457 invoked by uid 500); 8 Apr 2010 03:56:47 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 28448 invoked by uid 99); 8 Apr 2010 03:56:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Apr 2010 03:56:47 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of cinlung@gmail.com designates 74.125.83.45 as permitted sender) Received: from [74.125.83.45] (HELO mail-gw0-f45.google.com) (74.125.83.45) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Apr 2010 03:56:38 +0000 Received: by gwaa18 with SMTP id a18so892979gwa.18 for ; Wed, 07 Apr 2010 20:56:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:subject :date:mime-version:content-type:content-transfer-encoding:x-priority :x-msmail-priority:x-mailer:thread-index:x-mimeole:importance :in-reply-to; bh=orBoB3UGp9OkiojR2hL2swdVsYMP+VmamNIe2VKkfP8=; b=cLL1rJQiZs9tO3khTPjiefAg1F/GjpxHqzFJ19uW/jNoMxzj5XByU5YLRgOfF2Bk8E aryTvheMJ/wv/UvemLTCbbEz9nenyWzjR8jyqXSB4CMHx1Clc2cMDWhex1mu3rJJJiZ0 kDZYCJnbVktxDa1A8i4fekPVgcNxy0MluMyP4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:mime-version:content-type :content-transfer-encoding:x-priority:x-msmail-priority:x-mailer :thread-index:x-mimeole:importance:in-reply-to; b=Ohps5PSjQCjJfeaokCShacYyhc30t3ArGq718rGunt6Yh7RMB9avpF9MLIMiKQm7yd ez105dKgxpOucaZ+K+FV9e/zsl9cS3oSkyNAvVKpoeoxEhqWlAaL0e5XmaUHzLrWpDxM GY3r7RZ8GSRXzJIzPHcLryskEE8CBu4Flp8oQ= Received: by 10.101.145.4 with SMTP id x4mr21424286ann.11.1270698976454; Wed, 07 Apr 2010 20:56:16 -0700 (PDT) Received: from mobocinlung ([125.164.150.29]) by mx.google.com with ESMTPS id 6sm3743967yxg.48.2010.04.07.20.56.13 (version=SSLv3 cipher=RC4-MD5); Wed, 07 Apr 2010 20:56:15 -0700 (PDT) Message-ID: <4bbd53df.8602be0a.3105.1170@mx.google.com> From: "Cin Lung" To: "'Tomcat Users List'" Subject: Tomcat scalability settings Date: Thu, 8 Apr 2010 10:55:48 +0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 1 (Highest) X-MSMail-Priority: High X-Mailer: Microsoft Office Outlook, Build 11.0.5510 thread-index: AcrWzWCNZ9n64tNiTBe7fmWPIq66FgAALQyg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 Importance: High In-Reply-To: <28173804.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Dear All Dev Can anyone help me with my problem? I have two biggest problems as follow: 1. Multi Connection Problem: I have a web application that service to multiple users. Everytime the users accessing the server reach 100 users at the same time, the tomcat would slows down. I tried to set -xmx1024 and -xms1024, but it did not have any impact at all. I tried to set the memory cache to 2048 and above, but the tomcat won't start. My current server is running AMD Athlon 64 3000+ with 8GB memory running windows server 2003 SP1. I am running tomcat 6 for the app server. Before upgrading to Windows 2003 SP1 I also had the same problem. I thought by upgrading would make a difference, but it didn't. Is there any way to improve tomcat's performance. Will there be any use of Java NIO Framework in tomcat? I mean apache has Mina, why not combine with tomcat? 2. User cancellation problem Another thing that really bug me is that user would click on a web application that perform a very extensive task. The user was not patient and just close the browser accessing the app. This did not make that particular job stop. In fact the job is still running until finish and then it got no place to return the result since the user closed the browser. As the result, my server is working really hard and takes up all the resources available, and causes other users to lag. Is there any way to make that particular user task/thread stop working? Thank you in advance Rendra --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org