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 by
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 of
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
Yes, on Solaris it's 'kill -3 pid'. The thread dump will go to wherever you have
redirected stdout, catalina.out by default I believe.
-chris
-Original Message-
From: Geralyn M Hollerman [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2003 1:44 PM
To: [EMAIL PROTECTED]
Howdy,
Max threads for what? Request processor threads are controllable via
minProcessors and maxProcessors in the HTTP/1.1 connector element.
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Billy Ng [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 9:22 PM
To:
12 matches
Mail list logo
