Thank you David and Wade for this information.
I now have an idea what caused it. I have a fairly new programme that
uses too many threads, and I can deal with it.
However I would like to try the thread dump, but running kill -3 xxx
or kill -QUIT xxx on the first Tomcat thread found after
P.S. I've found the stack trace in catalina.out.
I thought I could pipe it to a file, but never mind.
Anyway thankyou for your help, I think I can get to the bottom of it all
now.
Wade Chandler wrote:
--- David Wall [EMAIL PROTECTED] wrote:
1) We have only a moderately busy site with
I've got Tomcat 4.1.30 and Apache 1.3 on Linux and I've been using the
jk2 connector for a year and a half without any problems.
Now I've suddenly got Tomcat stopping with the following message:
All threads (75) are currently busy, waiting. Increase maxThreads (75)
or check the servlet status
1) We have only a moderately busy site with about 500 new visitors
entering from outside every day, so it would have thought it would be
fairly difficult for them to use up all the 75 connections at the same
time, but I do have some programmes that create their own threads,
though in a
--- David Wall [EMAIL PROTECTED] wrote:
1) We have only a moderately busy site with about
500 new visitors
entering from outside every day, so it would have
thought it would be
fairly difficult for them to use up all the 75
connections at the same
time, but I do have some
How many threads can tomcat handle?
Assuming single tomcat hosting 5 different apps, no load balance, using
mod_jk and Apache.
I am wondering what would be the safe limit.
DarekC
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
Hi Darek,
This really depends on your operating system
We have MaxThreads set to 750 on our boxes running sarge.
You should however be aware that using that many threads in not
necessarily benifical as far as performance is concerned...
You should definitely do some performance testing.
We
From: Darek Czarkowski [mailto:[EMAIL PROTECTED]
Subject: What is max value for MaxThreads
How many threads can tomcat handle?
There's no single answer to this. The limit is a function of your
operating system and, to a lesser extent, your JVM heap parameters.
- Chuck
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
andrew wrote:
You should definitely do some performance testing.
We looked at using apache with mod_jk in front of our tomcats,
but this effectively halved the number of connections our servers
could handle per second, so in the end, we went
Resending...anyone know???
-Original Message-
From: Dan Carwin
Sent: Friday, November 05, 2004 11:01 AM
To: [EMAIL PROTECTED]
Subject: Tomcat 5 - coyote/jk2 connector defaults - maxthreads, timeout?
what is the default maxThreads in tomcat 5 jk2/coyote connector? What is
the default
what is the default maxThreads in tomcat 5 jk2/coyote connector?
What is the default serverTimeout ?
#channelSocket.serverTimeout=???
#channelSocket.maxThreads=???
(fwiw I'm referring to the version included in tc 5.0.28)
Thanks,
Dan
the MaxClients setting.
I increased the MaxClients amount in the Apache configuration file and
I wonder if I also need to increase the amount of threads handled by the
AJP connector as well (seems that the MaxThreads attribute is not
needed by the AJP connector )?
Is there a configuration
On Mon, 10 May 2004, Hollerman Geralyn M wrote:
| Evidently, I'm misunderstanding something about the maxThreads attribute
| on the HTTP Connector; I saw from the docs that in Tomcat 5.0.19, this
| is the maximum number of request processing threads to be created by
| this connector. So, what
Hi,
The new tomcat code have (finally!) an idea of connection queues, so
that
You just manage to hit a nerve with almost every post ;) This stuff has
been in tomcat code for years, it's not new.
Yoav
This e-mail, including any attachments, is a confidential business communication, and
may
On Wed, 12 May 2004, Shapira, Yoav wrote:
|
| Hi,
|
| The new tomcat code have (finally!) an idea of connection queues, so
| that
|
| You just manage to hit a nerve with almost every post ;)
I don't have a trace of an idea of what you mean!
;)
| This stuff has been in tomcat code for years,
Hi,
It wasn't there in earlier Tomcat 4s (-at least- not in 3.2), as Craig
didn't see the use for it. I rather clearly remember arguing rather
heavily for this some years ago, yes.
It was there in tomcat 4.0.1 and later. For tomcat 3.x I don't know but
I believe you do. I'm glad you argued
At 03:03 AM 5/11/2004 +, Bill Barker wrote:
By default, Tomcat will start maxThreads/2 threads incase it needs lots of
threads in a hurry. Almost all of them will be blocked, so there
generally
isn't that much OS overhead in creating them. However, if you set the
'maxSpareThreads
Hollerman Geralyn M [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Evidently, I'm misunderstanding something about the maxThreads attribute
on the
HTTP Connector; I saw from the docs that in Tomcat 5.0.19, this is the
maximum
number of request processing threads to be created
Evidently, I'm misunderstanding something about the maxThreads attribute on the
HTTP Connector; I saw from the docs that in Tomcat 5.0.19, this is the maximum
number of request processing threads to be created by this connector. So, what
that said to me was that if I wanted to allow lots
Howdy,
You might also use two tomcat instances -- much easier to tune.
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Parris, Edward G [mailto:[EMAIL PROTECTED]
Sent: Monday, February 02, 2004 5:38 PM
To: [EMAIL PROTECTED]
Subject: WHY? Tomcat 5 maxThreads too low
=0
useURIValidationHack=false disableUploadTimeout=true /
I tried a similar configuration on Tomcat 5.0.18 but noticed a ThreadPool warning on
startup stating that my maxThreads setting was too low and that it would be reset to
10.
WARNING: maxThreads setting (3) too low, set
=0
useURIValidationHack=false disableUploadTimeout=true /
I tried a similar configuration on Tomcat 5.0.18 but noticed a ThreadPool warning on
startup stating that my maxThreads setting was too low and that it would be reset to
10.
WARNING: maxThreads setting (3) too low, set
On Mon, February 2, 2004 at 2:38 pm, Parris, Edward G wrote:
I tried a similar configuration on Tomcat 5.0.18 but noticed a ThreadPool
warning on startup stating that my maxThreads setting was too low and that
it would be reset to 10.
WARNING: maxThreads setting (3) too low, set to 10
Does
David Rees wrote:
1. Recompile Tomcat 5, lowering the hard-coded minimum.
2. Implement a filter or some other type of synchronization in your
servlet which keeps track of the number of currently executing requests
and redirects the user to a different page with a meta refresh letting
them know
On Mon, February 2, 2004 at 6:28 pm, Josh Rehman wrote:
This brings up an interesting point. I'm too lazy to test it, but what
happens if you tomcat needs more threads than it is allowed? Does the
user get a 404?
No. If the acceptCount is set to more than 0, the request will sit in the
, January 20, 2004 2:16 AM
To: [EMAIL PROTECTED]
Subject: Re: maxProcessors vs maxThreads
Oh, come on, get real :). The Jk-Coyote docs are probably second to the
mod_jk2 docs for being the most incomplete. While (as Remy has stated),
you
can perfectly happily set
I'd go with 'or'. In the TC 3.x line, the HTTP Connector really s*cked
(except that with the TC 3.3.2-dev nightly, you have the option of using the
same CoyoteConnector as TC 4.1.x-5.0.x :). Unless you *need* the features of
e.g. mod_rewrite, mod_php, I'd agree with Yoav, and you should use
Oh, come on, get real :). The Jk-Coyote docs are probably second to the
mod_jk2 docs for being the most incomplete. While (as Remy has stated), you
can perfectly happily set this on the Connector, the jk2.properties syntax
is:
container.maxThreads=value
Shapira, Yoav [EMAIL PROTECTED] wrote
Howdy,
Oh, come on, get real :). The Jk-Coyote docs are probably second to
the
mod_jk2 docs for being the most incomplete.
We should probably do something about that, then ;) I've paid much more
attention to the tomcat (core) docs rather than the connector-related
stuff, naturally, as I don't
the connectors, is that because there is
something better to use?
ADC
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: 20 January 2004 13:57
To: Tomcat Users List
Subject: RE: maxProcessors vs maxThreads
Howdy,
Oh, come on, get real :). The Jk-Coyote docs are probably
Is there a similar setting for jk2 under 4.1.29?
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker
Sent: Tuesday, January 20, 2004 2:16 AM
To: [EMAIL PROTECTED]
Subject: Re: maxProcessors vs maxThreads
Oh, come on, get real :). The Jk-Coyote docs
Howdy,
You seem to know what you are talking about and it amuses me everyday
you
come on at the same sort of time and bang off all the answers :)
(although
regrettably I was hoping you would answer my Tomcat and Clusters one
yesterday).
I work normal hours, roughly 8:30-4:30 at my day job, US
: maxProcessors vs maxThreads
Hi Yoav,
Anyways, if someone like you is not using the connectors, is
that because there is something better to use?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
: maxProcessors vs maxThreads
Howdy,
You seem to know what you are talking about and it amuses me everyday
you
come on at the same sort of time and bang off all the answers :)
(although
regrettably I was hoping you would answer my Tomcat and Clusters one
yesterday).
I work normal hours, roughly 8:30-4:30
Howdy,
Hm, we have setup IIS in front of Tomcat so it can serve off the static
content, I thought that was the conventional wisdom.
Conventional and/or outdated. Or is the more likely operator in the
previous sentence.
We're looking at about 300+ users of which maybe lets say 20 concurrent
at
Thanks Yoav.
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: 20 January 2004 16:12
To: Tomcat Users List
Subject: RE: maxProcessors vs maxThreads
Howdy,
Hm, we have setup IIS in front of Tomcat so it can serve off the static
content, I thought
there seems to be some confusion about whether to use maxThreads or
maxProcessors and the effect on tomcat. futher it is not clear from the
docs which one to use and whether they have an effect on the protocol used
by the connector.
could someone please clarify this...
using tomcat 5.0.16
Howdy,
there seems to be some confusion about whether to use maxThreads or
maxProcessors and the effect on tomcat. futher it is not clear from the
docs which one to use and whether they have an effect on the protocol
used
by the connector.
Read the documentation carefully. The Coyote (HTTP
of memory? or is there
behaviour as specified by the acceptcount/max processors for the http
connector buried in the code of the ajp connector that can't be modified?
thanks in advance.
Howdy,
there seems to be some confusion about whether to use maxThreads or
maxProcessors and the effect on tomcat
Shapira, Yoav wrote:
Howdy,
there seems to be some confusion about whether to use maxThreads or
maxProcessors and the effect on tomcat. futher it is not clear from the
docs which one to use and whether they have an effect on the protocol
used
by the connector.
Read the documentation carefully
Howdy,
thanks yoav, i noticed that but then does that mean that there is no
method to specify max threads/processors for the coyote ajp connector?
that sounds a bit strange
If it's not documented, then there's no configurable way to do it. Of
course, you can always subclass/extend a
(tomcat is always hidden behind apache on an internal network not
accessible from the outside) what parameters should i use to judge whether
to use http or ajp connectors?
it seems like http is better (due to the fact that you can customize
settings like maxThreads) but i was always under the impression
On Mon, January 19, 2004 at 1:47 pm, Apu Shah wrote:
this begs another question... under what circumstances would one choose to
use the ajp connector? i am assuming it's probably a more compact and
efficient protocol compared to http (not sure about that).
The AJP protocol is designed to be
directly
from a browser (tomcat is always hidden behind apache on an
internal network not accessible from the outside) what
parameters should i use to judge whether to use http or ajp
connectors?
it seems like http is better (due to the fact that you can
customize settings like maxThreads) but i
thanks much remy. i was looking for configuring maxThreads for the ajp
connector with jk2.
anyways, do you know what the default value for maxThreads is for
channelSocket? (it's not in the docs)
what are the defaults for the other options? or where can i find them?
backLog
tcpNoDelay
using tomcat 5.0.16
the JK2 AJP connector
(http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/ajp.html) docs
doesn't list any directive like maxProcessors or maxThreads. the HTTP
connector does
(http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/http.html) list a
maxThreads directive.
1
: All threads (150) are currently busy, waiting. Increase
maxThreads (150) or check the servlet status
alan sparago wrote:
I am using Tomcat 5.0.16 standalone serving as both an http/https web
server
and servlet container. This error occurred in our QA environment and has
caused Tomcat to hang
sparago [mailto:[EMAIL PROTECTED]
Sent: Thu 12/25/2003 12:45 AM
To: [EMAIL PROTECTED]
Cc: Dave McCuistion
Subject: All threads (150) are currently busy, waiting. Increase maxThreads (150) or
check the servlet status
I am using Tomcat 5.0.16 standalone serving as both an http/https web server
. Most parameters in
the server.xml file are the default values (the maxThreads value is set to
150).
Our log file is in xml format and contains the following error;
loggerorg.apache.tomcat.util.threads.ThreadPool/logger
levelSEVERE/level
classorg.apache.tomcat.util.threads.ThreadPool/class
in
the server.xml file are the default values (the maxThreads value is set to
150).
Our log file is in xml format and contains the following error;
loggerorg.apache.tomcat.util.threads.ThreadPool/logger
levelSEVERE/level
classorg.apache.tomcat.util.threads.ThreadPool/class
methodlogFull
Hi all ,
I'm using tomcat 4.1.17 / apache 1.3.26 / mod_jk 1.2.2.
Sometimes, I found this message in my catalina.out file :
7 nov. 2003 09:12:35 org.apache.tomcat.util.log.CommonLogHandler log
INFO: All threads are busy, waiting. Please increase maxThreads or check the
servlet status10 10
Howdy,
It's the maxProcessors attribute of the Connector element
in server.xml.
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: AMELIN Franck [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2003 6:43 AM
To: 'Tomcat Users List'
Subject: Please increase maxThreads
I am getting this message in my catalina.out file: SEVERE: All threads
are busy, waiting. Please increase maxThreads or check the servlet
status500 500; I have no idea why all threads would be busy and
waiting.
In the standard distribution of Tomcat 4.1.24, the value of maxThreads
is 75
The first thing you need is a thread dump of the Tomcat process at the time you are
experiencing all threads busy. You are 100% correct in your assumption that raising
maxThreads will just delay the inevitable. Once you have a thread dump you can
investigate what section of code has all
Running against a database? Are you pooling the connections? We hit
maxthreads when either the DB is messed up (i.e., someone locks a table)
or before, when the programmers forgot to run socket_close() on the DB
connection, thereby returning it to the pool.
HTH,
Ben Ricker
On Mon, 2003-08-18
Ben Ricker wrote:
Running against a database? Are you pooling the connections? We hit
maxthreads when either the DB is messed up (i.e., someone locks a table)
or before, when the programmers forgot to run socket_close() on the DB
connection, thereby returning it to the pool.
Why, yes I am
On Mon, 2003-08-18 at 12:50, Geralyn M Hollerman wrote:
Ben Ricker wrote:
Running against a database? Are you pooling the connections? We hit
maxthreads when either the DB is messed up (i.e., someone locks a table)
or before, when the programmers forgot to run socket_close() on the DB
: Re:maxThreads
Halstead, Chris wrote:
The first thing you need is a thread dump of the Tomcat
process at the time you are experiencing all threads busy.
You are 100% correct in your assumption that raising
maxThreads will just delay the inevitable. Once you
have a thread
Hi folks;
Would anybody tell me if there is a way to change the maxThreads for Tomcat 4.0? I
don't see the option in server.xml
Thanks!
Billy Ng
To: Tomcat Users List
Subject: maxThreads Settingd
Hi folks;
Would anybody tell me if there is a way to change the maxThreads for
Tomcat
4.0? I don't see the option in server.xml
Thanks!
Billy Ng
This e-mail, including any attachments, is a confidential business communication, and
may contain
60 matches
Mail list logo
