tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From DirectXtras <postmas...@directxtras.com>
Subject Autoreply: Re: Tomcat performance issue?
Date Sat, 10 Apr 2004 19:45:24 GMT
Hello,

Due to the increased volume of SPAM this mailbox has been closed.

Please contact us via http://www.directxtras.com/ContactUS.asp

We apology for the inconvenience.

Best Regards,
--
The DirectXtras Team
---------------------------------------------------------------------
DirectXtras - Xtra Power for Director and Authorware -
              http://www.directxtras.com
Sites with something to say - http://www.SpeaksForItself.com
---------------------------------------------------------------------


Your message reads:

Received: from mail.apache.org (unverified [208.185.179.12]) by mail2.intermedia.net
 (Rockliffe SMTPRA 4.5.6) with SMTP id <B0312920521@mail2.intermedia.net> for <postmaster@directxtras.com>;
 Sat, 10 Apr 2004 12:45:24 -0700
Received: (qmail 61062 invoked by uid 500); 10 Apr 2004 19:45:04 -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 61040 invoked from network); 10 Apr 2004 19:45:03 -0000
Received: from unknown (HELO main.gmane.org) (80.91.224.249)
  by daedalus.apache.org with SMTP; 10 Apr 2004 19:45:03 -0000
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 1BCOPc-0001fg-00
	for <tomcat-user@jakarta.apache.org>; Sat, 10 Apr 2004 21:45:08 +0200
Received: from lsanca1-ar19-4-46-072-212.lsanca1.dsl-verizon.net ([4.46.72.212])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <tomcat-user@jakarta.apache.org>; Sat, 10 Apr 2004 21:45:08 +0200
Received: from wbarker by lsanca1-ar19-4-46-072-212.lsanca1.dsl-verizon.net with local (Gmexim
0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <tomcat-user@jakarta.apache.org>; Sat, 10 Apr 2004 21:45:08 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: tomcat-user@jakarta.apache.org
From: "Bill Barker" <wbarker@wilshire.com>
Subject: Re: Tomcat performance issue?
Date: Sat, 10 Apr 2004 12:58:23 -0700
Lines: 35
Message-ID: <c59is1$4c8$1@sea.gmane.org>
References: <468E4BCF164C944E88DF9F70D15FFA751377AC@complusexch1.complusdata.hq> <4077A03F.1090004@greenhydrant.com>
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: lsanca1-ar19-4-46-072-212.lsanca1.dsl-verizon.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Sender: news <news@sea.gmane.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


"David Rees" <drees@greenhydrant.com> wrote in message
news:4077A03F.1090004@greenhydrant.com...
> Denise Mangano wrote, On 4/9/2004 10:05 PM:
> >
> > I've tried searching the archives but have come up empty-handed.  A few
> > days ago I received a few complaints that my users hit a certain point
> > in the application and could go no further.  This point was when Apache
> > gives control to Tomcat.  I checked the log and found this.
> >
> > Apr 4, 2004 2:19:43 PM org.apache.tomcat.util.threads.ThreadPool logFull
> > SEVERE: All threads (75) are currently busy, waiting. Increase
> > maxThreads (75) or check the servlet status
> >
> > The only thing that did the trick was restarting Tomcat and Apache.  Any
> > ideas on what these errors mean?
>
> Like the messages say, all Tomcat threads are busy and you've hit the
> maximum number of threads which can be processed concurrently.  Sounds
> like you've got either a bug in a servlet causing it to not return, or
> your server is simply overloaded.  You can get a stack trace from the
> JVM to help debug this issue pretty easily.
>

Also, when running behind Apache, you have need to have at least as many
Tomcat threads as you have Apache children allowed (since each child will be
talking to a single thread).  You should probably increase the maxThreads on
you AJP/1.3 Connector to match what you've configured for MaxChildren in
Apache.  If you expect your loads to come in bursts, then you can configure
maxSpareThreads low to allow Tomcat to discard threads that are freed up by
Apache killing off children.

> -Dave




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



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


Mime
View raw message