: Peter Bauer [EMAIL PROTECTED]
An: Tomcat Users List users@tomcat.apache.org
Betreff: All threads busy + OutOfMemoryError
Hi all,
i thought i had solved the All threads busy problem by implementing a
dedicated servlet class for forwarding requests but maybe i was wrong or
there is another
concurrent connections to a single servlet
(weird?!), then you might end up with lots of stalled threads
(potentially 395 of them) waiting for those 5 magic slots.
Each thread needs 2 MB per thread then
Is that an observation, or a guess?
JVM heap size max = 400 * 2 MB (1GB) + 20
Thanks Chris for the response.
-Venky
-Original Message-
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Sent: Monday, October 22, 2007 1:04 PM
To: Tomcat Users List
Subject: Re: Number of Threads in request processing pool and JVM heap
size
-BEGIN PGP SIGNED MESSAGE
I have 80 servlets on tomcat and each of them can have 5 five concurrent
requests to be processed as per design.
Tomcat Connectors specification says
maxSpareThreads
The maximum number of unused request processing threads that will be
allowed to exist until the thread pool starts stopping
You'd do something like
req.getRequestDispatcher(/contextRel/path/to/logoutUrl).forward( req,
resp ). All of the request parameters available to the current servlet
would be passed on to the logout servlet.
--David
Peter Bauer wrote:
Am Donnerstag 18 Oktober 2007 schrieb Christopher
Am Donnerstag 18 Oktober 2007 schrieb Christopher Schultz:
Peter,
This next method call is the problem. I am sending a POST request from
one servlet instance to another one. But in situations with high load,
all 20 instances are busy, so the ActiveRoleRemoval.sendLogoutMessages
method
---
- Original Message -
From: Peter Bauer [EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Wednesday, October 17, 2007 10:52 AM
Subject: All threads are currently busy
Hi all,
System:
Tomcat 4.1.30 on Debian sarge
java version 1.5.0_11
Java(TM) 2 Runtime Environment
---
- Original Message -
From: Peter Bauer [EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Wednesday, October 17, 2007 5:24 PM
Subject: Re: All threads are currently busy
Good afternoon Martin :-)
On Wednesday 18 October 2000 16:08:34 you wrote:
Good Morning Peter
I assume
This next method call is the problem. I am sending a POST request from one
servlet instance to another one. But in situations with high load, all 20
instances are busy, so the ActiveRoleRemoval.sendLogoutMessages method which
sends the POST request blocks because there is no other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
This next method call is the problem. I am sending a POST request from one
servlet instance to another one. But in situations with high load, all 20
instances are busy, so the ActiveRoleRemoval.sendLogoutMessages method which
sends the
to recover from that status. In the catalina.out file, i get the following line:
SEVERE: All threads (75) are currently busy, waiting. Increase maxThreads (75)
or check the servlet status
i searched some time in various forums and mailing list archives and found the
following links:
http://mail
),
failedRoles.getEl2(index),
isNam);
}
}
}
specifically are there higher priority threads currently executing so
perhaps yield to those threads may apply?
http://java.sun.com/j2se
[EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Wednesday, October 17, 2007 10:52 AM
Subject: All threads are currently busy
Hi all,
System:
Tomcat 4.1.30 on Debian sarge
java version 1.5.0_11
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
Java HotSpot(TM) Client VM
[EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Wednesday, October 17, 2007 5:24 PM
Subject: Re: All threads are currently busy
Good afternoon Martin :-)
On Wednesday 18 October 2000 16:08:34 you wrote:
Good Morning Peter
I assume you have built glibc for debian following the specific build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
Peter Bauer wrote:
This version of TC is quite old ..not sure if its supported anymore
Yes, i know about that. If there is a major bug in this version, i could
argue to upgrade
(at least to the last 4.1.x version) but i would need some
Manivannan Palanichamy wrote:
I need to design a web application that may use threads. Thats, the web
application might have to read some 200 files from network. In order to
speed up the process, I've decided to use threads/thread pooling. But,
however I know it is not a good practice to use
Hi
I need to design a web application that may use threads. Thats, the web
application might have to read some 200 files from network. In order to
speed up the process, I've decided to use threads/thread pooling. But,
however I know it is not a good practice to use threads in a web/server
request to the same
session blocks until one of the other requests return/finishes.
It seems to me that the tomcat (v 5.5) limits the number of threads per
session to 3. I would like
to increase this number to prevent blocking of further requests.
How can I adjust this setting ?
Greetings
Andree
I doubt tomcat limits the number of Threads per session. To get the
session id, tomcat need to parse the request, but this parsing occurs in
the Http-Thread that handle that network connection. Having that
HTTP-thread wait would be, for tomcat, wasting a Thread.
On the other hand, it's common
From: Riechert, Andree [mailto:[EMAIL PROTECTED]
Subject: Concurrent threads per session (limit = 3 ?)
It seems to me that the tomcat (v 5.5) limits the number of
threads per session to 3.
As David pointed out, it's not Tomcat imposing a limit - it's Firefox
complying
request when a second one comes in.
Well, once the requests are synchronized, I'd like to give users an ability
to change their mind and not wait until the first request finishes. That is
the main justification for interrupting threads. It will allow for a more
responsive interaction with the UI
for interrupting threads. It will allow for a more
responsive interaction with the UI. There is an article with a good example
of request synchronization:
http://www.onjava.com/pub/a/onjava/2004/03/24/loadcontrol.html.
Hope it's clear now why I'm asking about interrupting threads - vetoing
users@tomcat.apache.org
To: Tomcat Users List users@tomcat.apache.org
cc: keif [EMAIL PROTECTED]
Subject:Re: Interrupting tomcat threads.
On Fri Jul 20 15:23:45 CEST 2007 Tomcat Users List
users@tomcat.apache.org wrote:
Christopher Schultz-2 wrote:
So, multiple simultaneous
this be accomplished by interrupting threads? Should I spawn new threads
for such processing and manage them instead of working with threads given by
the container?
Thank you,
keif.
--
View this message in context:
http://www.nabble.com/Interrupting-tomcat-threads.-tf4113604.html#a11697335
Sent
this be accomplished by interrupting threads? Should I spawn new threads
for such processing and manage them instead of working with threads given by
the container?
I think you can do this (but I still don't understand why you'd want
to). You could do something like this:
1. Writer a filter
that you proposed.
Thank you for a quick reply,
keif.
--
View this message in context:
http://www.nabble.com/Interrupting-tomcat-threads.-tf4113604.html#a11698350
Sent from the Tomcat - User mailing list archive at Nabble.com
threads on the server side.
I would also recommend vetoing the /second/ request, rather than
canceling the first request when a second one comes in. You should have
each synchronous request report some kind of success state, so that
when the second request fails, the UI doesn't update inappropriately
André,
André Vila Cova wrote:
And it's possible to know what threads are really doing?
And I don't understand why having the following 3 connectors
maxThreads=400 minSpareThreads=25 maxSpareThreads=75
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
maxThreads=150 minSpareThreads=25
this looks like a deadlock.
I agree with Chuck: this is just an Object.wait() being called on the
ControlRunnable object (which is probably the monitor for the thread
pool). Most threads will be in this state. If you have threads in this
state, then they are /not/ busy... they're waiting around
And it's possible to know what threads are really doing?
And I don't understand why having the following 3 connectors
maxThreads=400 minSpareThreads=25 maxSpareThreads=75
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
I get error
is doing?
Thank You
On 7/11/07, Titi Wangsa [EMAIL PROTECTED] wrote:
probably some threads are performing database operation
and it takes too long so new threads are being spawned,
the new threads are also taking too long, so newer threads are being
spawned.
too much spawning, that is what
-
Djava.util.logging.conf
Output is null when I execute the following command:
[EMAIL PROTECTED] ~]# kill -QUIT 6404
[EMAIL PROTECTED] ~]#
How can I see what thread is doing?
Thank You
On 7/11/07, Titi Wangsa [EMAIL PROTECTED] wrote:
probably some threads are performing database operation
is too long
for any busy site of course.
Before you examine all your threads you should test your application for such
errors that delay the answer to requests.
Maybe you should also try to build a test setup, answering very simple to your
requests (hello, world) and push in one application module
the connector had it's
retry
flag on. So the answer to each request was, trying to connect to a
unconnectable database until the timeout has been reached, which is too
long
for any busy site of course.
Before you examine all your threads you should test your application for
such
errors
the timeout has been reached, which is
too long
for any busy site of course.
Before you examine all your threads you should test your application
for such
errors that delay the answer to requests.
Maybe you should also try to build a test setup, answering very simple
to your
Am Donnerstag, 12. Juli 2007 19:12 schrieb André Vila Cova:
Lot of waits... Could you help me?
http-8085-Processor24 daemon prio=1 tid=0x082f1378 nid=0x19c6 in
Object.wait() [0xde118000..0xde118e20]
at java.lang.Object.wait(Native Method)
- waiting on 0xe619f748 (a
From: Ingo Krabbe [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat - All threads (200) are currently busy
http-8085-Processor24 daemon prio=1 tid=0x082f1378 nid=0x19c6 in
Object.wait() [0xde118000..0xde118e20]
at java.lang.Object.wait(Native Method)
- waiting
(a
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
somehow this looks like a deadlock.
I agree with Chuck: this is just an Object.wait() being called on the
ControlRunnable object (which is probably the monitor for the thread
pool). Most threads will be in this state. If you have threads in this
state
on the
ControlRunnable object (which is probably the monitor for the thread
pool). Most threads will be in this state. If you have threads in this
state, then they are /not/ busy... they're waiting around for something
to do!
-chris
Hello!
I get lot of times the following error:
SEVERE: All threads (200) are currently *busy*, waiting. *Increase
maxThreads*
**
*Strange is that i've configured in server.xml the following
(maxThreads=400):*
*
Connector
port=8085 maxHttpHeaderSize=8192
maxThreads
André Vila Cova wrote:
Hello!
I get lot of times the following error:
SEVERE: All threads (200) are currently *busy*, waiting. *Increase
maxThreads*
**
*Strange is that i've configured in server.xml the following
(maxThreads=400):*
*
You have probably done that for a wrong connector
I don't think so... I will see..but, why i get the error?
SEVERE: All threads (200) are currently *busy*, waiting. *Increase
On 7/11/07, Mladen Turk [EMAIL PROTECTED] wrote:
André Vila Cova wrote:
Hello!
I get lot of times the following error:
SEVERE: All threads (200) are currently
cause your threads are all busy serving requests (or hanging
somewhere). Perform a thread dump with kill -QUIT and you'll see what
they are doing.
regards
Leon
On 7/11/07, André Vila Cova [EMAIL PROTECTED] wrote:
I don't think so... I will see..but, why i get the error?
SEVERE: All threads
probably some threads are performing database operation
and it takes too long so new threads are being spawned,
the new threads are also taking too long, so newer threads are being spawned.
too much spawning, that is what is causing the limit break.
On 7/12/07, André Vila Cova [EMAIL PROTECTED
to solve my problem
another way (MDB comes into my mind).
Thanks again,
Mirek
On 7/2/07, Johnny Kewl [EMAIL PROTECTED] wrote:
- Original Message -
From: Rainer Jung [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Monday, July 02, 2007 8:24 PM
Subject: Re: Tomcat Threads
Dear All,
I have a problem when too few (only 2) Tomcat's threads is handling my
requests.
First a little background on what I'm trying to do:
I have an web application, which loads a page. On loading the page there are
Ajax script calls (DWR framework),
requesting more data from the tomcat
with.
Fun along the way :D
Now the problem. I can see only 2 Tomcat Threads, handling all of these
request, which as you can imagine can take a while.
Shouldn't tomcat take a new Thread from the Thread Pool for each
Request up
to Maximum? Am I missing some configuration Tricks?
Here is the thread
From: Mirek Kopriva [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat Threads handling user Requests problem
Now the problem. I can see only 2 Tomcat Threads, handling
all of these request, which as you can imagine can take a while.
This is the result of the browser complying with the HTTP RFC
From: Caldarale, Charles R
Subject: RE: Tomcat Threads handling user Requests problem
There is a registry setting you can tweak in Windows to let
IE6/7 open more than 2 at a time; there's probably something
equivalent in Firefox, but I don't know what it is.
For IE, look here:
http
it will change, but you just going to be happier anyway
;)
- Original Message -
From: Mirek Kopriva [EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Monday, July 02, 2007 3:55 PM
Subject: Tomcat Threads handling user Requests problem
Dear All,
I have a problem when too few (only 2
@tomcat.apache.org
Sent: Monday, July 02, 2007 7:34 PM
Subject: Re: Tomcat Threads handling user Requests problem
Can you believe that, IE only allows 2 files downloaded at the same time,
and then you have to dig into the registry get OPERA ;)
Now that I advertised my favorite browser
I think
Johnny Kewl wrote:
Can you believe that, IE only allows 2 files downloaded at the same
time, and then you have to dig into the registry get OPERA ;)
The 2 connections are a recommendation for well-behaved http clients
coming from the http spec in order to keep server load related to one
- Original Message -
From: Rainer Jung [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Monday, July 02, 2007 8:24 PM
Subject: Re: Tomcat Threads handling user Requests problem
Johnny Kewl wrote:
Can you believe that, IE only allows 2 files downloaded
Hi all,
I have an Embedded Tomcat, and my question is:
- How should I do to retrieving the information about the number of
currently working threads using the Tomcat API?
Thanks in advance,
Best regards
Raffaele
--
View this message in context:
http://www.nabble.com/Retrieving-working
Hi All,
I am frequently getting this error in tomcat which stops my tomcat service.
Pl help me its urgent and costing my service as well:
I am getting bellow error in my catalina logs:
Jun 19, 2007 5:55:44 PM org.apache.tomcat.util.threads.ThreadPool logFull
SEVERE: All threads (250
:44 PM org.apache.tomcat.util.threads.ThreadPool
logFull
SEVERE: All threads (250) are currently busy, waiting. Increase
maxThreads
(250) or check the servlet status
Hi Prashant,
You may want to increase your 'maxThreads' setting in conf/server.xml
Connector port=8080 maxHttpHeaderSize
Do as it says and increase the max threads parameter or manage your threads
better.
Robert S. Harper
Senior Engineer
Information Access Technology, Inc.
1100 East 6600 South, Suite 300
Salt Lake City Utah USA 84121-7411
(801)265-8800 Ext. 255
FAX (801)265-8880
This e-mail is intended only
as it says and increase the max threads parameter or manage your
threads
better.
Robert S. Harper
Senior Engineer
Information Access Technology, Inc.
1100 East 6600 South, Suite 300
Salt Lake City Utah USA 84121-7411
(801)265-8800 Ext. 255
FAX (801)265-8880
This e-mail is intended only for the addressee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/06/2007, at 4:45 PM, Prashant Thakkar wrote:
Hi,
Thanks,
But this is the clients application which we are running. We dont
have the
access to the servlet code. That was the the obvious reason we had
increased
the thread limit to 250.
[EMAIL PROTECTED] wrote:
Do as it says and increase the max threads parameter or manage your
threads
better.
Robert S. Harper
Senior Engineer
Information Access Technology, Inc.
1100 East 6600 South, Suite 300
Salt Lake City Utah USA 84121-7411
(801)265-8800 Ext. 255
FAX (801)265-8880
This e-mail
Hi,
I read an abt thread pooling on below url:
http://www.hp.com/products1/unix/webservers/apache/techtips/tomcat.html
Thanks and Regards,
-Prashant Thakkar
On 6/19/07, Andrew Miehs [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/06/2007, at 4:45 PM, Prashant
connectionTimeout=2
proxyPort=80 disableUploadTimeout=true /
--
Thanks and Regards,
- Prashant Thakkar
On 6/19/07, Robert Harper [EMAIL PROTECTED] wrote:
Do as it says and increase the max threads parameter or manage your
threads
better.
Robert S. Harper
Senior Engineer
redirectPort=8443 acceptCount=100
debug=0 connectionTimeout=0
disableUploadTimeout=true /
You almost certainly don't want connectionTimeout=0. That will tie up
threads until the browser decides to drop the connection.
!-- Note : To disable connection timeouts, set connectionTimeout
, the most important
thread is main, with 9666 ticks, closely
followed by:
TP-processor4 (9470 ticks)
After this I get a list of
http10722-processorN threads, with ticks
running down from 4580 - 487
all other threads have very few ticks.
On examining function profiles for these threads,
it is clear
minutes with big applications)
but occurs only once per life of jvm.
followed by:
TP-processor4 (9470 ticks)
I think they handle various connections of tomcat before dispatching
them to http-thread, modjk thread or alike. But not sure.
After this I get a list of
http10722-processorN threads
Adam Rabung wrote:
I _know_ I'll eventually discover this is some configuration problem
on my end, I'm just trying to understand the life-cycle of the
JspRuntimeContext to help me track it down. I'm still stumped.
I should have looked at the code rather than relying on my dodgy
memory. This
Adam Rabung wrote:
Any advice would be much appreciated.
Had the contexts been reloaded at any point? If so, is there a rough
correlation between the number of threads per context and the number
of reloads?
Mark
-
To start
I have now been able to make it work on another minimalistic server
using the same worker.properties. It displays the runtime state. Now I
only have to find out what differs, that makes the status worker fail
getting runtime state. (It's a lot that differs so that may take a long
time :-/ )
Hello,
Tomcat 5.5.9/Windows XP/Java 1.5_11
I have a Tomcat running about 16 contexts. A few of them are fairly busy.
We recently had a Out of memory: unable to create new native thread
Exception. At the time, we had roughly 500 threads in the VM. Of that, 147
were named JSPRuntimeContext
Please open a bugzilla issue and attach the relevant parts of your
mod_jk config (jk directives from httpd.conf and workers.propertiers and
uriworkermap.orperties, if applicable).
Erik Melkersson schrieb:
Thanks for the info but unfortunately I don't think that is is case for
me. I surfed to a
N/A as a state means, that no requests have been sent to this worker for
some time. So mod_jk is not really able to tell you about the state of
the worker. It can only detect OK, ERROR etc. when it is sending
requests to the workers. No requests, no state.
A worker will be in state N/A
Thanks for the info but unfortunately I don't think that is is case for
me. I surfed to a mapped address and got pages back from the tomcat
trough the workers and still had N/A as state. I've also used it and got
an error message back (both tomcats blocked) but the state was still N/A.
As I
Does anyone recognize my problem about the runtime state that never is
displayed or did it work for you out-of-the-box?
Regards Erik Melkersson
Erik Melkersson wrote:
Hi!
I've got an apache (1.3.33) with mod_jk (1.2.21) connecting to two
tomcats (5.5.17) on other servers using a load
Hi!
I've got an apache (1.3.33) with mod_jk (1.2.21) connecting to two
tomcats (5.5.17) on other servers using a load balacer. (All running
debian.) I also have mounted a jkstatus on a directory.
My problem is that the jkstatus is never displaying the runtime state of
the workers. I always
that, althougt I've set Max
Threads to 9000, Tomcat server won't accept more than 300 concurrent
connections?!
I know there are some solutions around like coninuations introduced in Jetty
6, but there's still no solution for Tomcat (at least not in version 5.5)? Or
am I missing something
Many thanks!
On 29/01/07, Bill Au [EMAIL PROTECTED] wrote:
If you are spawning threads from your servlet, make sure that they are
cleaned up when
the servlet is destroyed. Otherwise, you will have a thread leak. I have
ran into this problem
when the webapp is reloaded without restarting
: multiple requests from the same client (only 2 threads are
activated!)
Hi,
I have a web application and I'm using ajax to send requests to the server
(I'm using Tomcat 5.5.17).
The problem is the following:
- if I send more than two requests from the same client, the third
request
threads are
activated!)
Are you using firefox as web client?
There's an issue of firefox (i don't know what is) what only 2 downloads are
performed as same time.
-Mensaje original-
De: Debora Desideri [mailto:[EMAIL PROTECTED] Enviado el: jueves, 25 de enero
de 2007 19:49
Para: users
From: Mike Quilleash [mailto:[EMAIL PROTECTED]
Subject: RE: multiple requests from the same client (only 2
threads areactivated!)
I believe the HTTP 1.1 spec specifies that a maximum of two
simultaneous connections should be allowed by a remote client
to a server.
The spec defines
Hi,
I would be grateful is someone could answer these questions:
* Can servlets safely spawn threads?
* If so, under what conditions?
I tried to find the answers searching the web, but found conflicting views.
So I thought it worth asking about a specific servlet container
implemention.
I'm
En l'instant précis du 01/29/07 11:33, Danny Ayers s'exprimait en ces
termes:
Hi,
I would be grateful is someone could answer these questions:
* Can servlets safely spawn threads?
short answer, yes. They *can*. However that does not mean all spawned
Threads are safe.
* If so, under what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Danny,
David Delbecq wrote:
1) Your servlet must always take care to finish all Threads it has
spawned. This mean when servlet gets unloaded, you must have provided a
mecanism in your servlet to stop all running threads your servlet has
created
If you are spawning threads from your servlet, make sure that they are
cleaned up when
the servlet is destroyed. Otherwise, you will have a thread leak. I have
ran into this problem
when the webapp is reloaded without restarting the server. Each leaked
thread has a
reference to its classloader
, 2007 11:30 PM
Subject: RE: multiple requests from the same client (only 2 threads are
activated!)
From: Debora Desideri [mailto:[EMAIL PROTECTED]
Subject: multiple requests from the same client (only 2
threads are activated!)
- if I send more than two requests from the same client,
the third
Hi,
I have a web application and I'm using ajax to send requests to the server (I'm
using Tomcat 5.5.17).
The problem is the following:
- if I send more than two requests from the same client, the third request
is not executed until one of the other two has been executed. It seems
From: Debora Desideri [mailto:[EMAIL PROTECTED]
Subject: multiple requests from the same client (only 2
threads are activated!)
- if I send more than two requests from the same client,
the third request is not executed until one of the other two
has been executed.
Assuming your
Hi all,
I have two servlets: Worker and Status. Worker servlet gets hit very
frequently and consumes all available Tomcat threads (configured via
maxThreads). Thus, whenever I try to access the Status thread I have to wait
a long time. Is there a way to either dedicate some threads to Status
Hi
I am fighting with Tomcat for a couple of days and I cannot find a cause
to the problem.
I am using Tomcat 5.5.16 and it is configured to run HTTP on port 8081
and HTTPS on port 8444.
The problem:
The application runs properly over HTTP. However over HTTPS the number
of threads keep
Andrew Friebel wrote:
I finally managed to get the email. I had to request it using
users-get.
Am I supposed to get the mail automatically?
You are subscribed to the digest list. The Reply-To header is missing
on the digest list so mail clients don't know where to send the reply.
I'll get
This is going to seem like a real stupid question, but there seems to be
no obvious way for me to reply to responses on threads. I have tried to
use users-help and users-info email addresses to get this information,
but they keep giving me automatic responses.
How do I reply to a given thread
of the group. But since you got this message
sent to the list, you are. So go ahead and try respond to this message.
Justin
- Original Message
From: Andrew Friebel [EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Thursday, November 9, 2006 6:53:56 PM
Subject: Replying to threads
]
Sent: Friday, 10 November 2006 1:46 PM
To: Tomcat Users List
Subject: Re: Replying to threads
Well, I suppose it depends on your email client. But on almost all
clients, open the message (or thread response which you wish to add to)
and click the 'Reply' button in your email client. Then write
What I observe is:
a) A certain amount of free memory is required to instantiate a web application
b) Concurrent requests are handled by separate HTTP Processor threads
c) The maxSpareThreads attribute of the HTTP Connector is not honored until GC
And when I:
1) Deploy three helloworld Turbine
From: Ryan Gies [mailto:[EMAIL PROTECTED]
Subject: OutOfMemory Exceptions and HTTP Processor Threads
I will get OutOfMemory Exceptions because there is no free
memory to instantiate the 3rd webapp, as the idle HTTP
Connectors have consumed all available memory.
May or may not have
Hello,
How many threads tomcat with APR and without APR uses to handle
keep-alive connections?
As I understand tomcat without APR uses 1 thread per keep-alive
connection as tomcat does not use NIO.
APR may use epoll to handle keep-alive connections
http://tomcat.apache.org/tomcat-5.5-doc
Check your connectiontimeout value. May be it is too high ?
Have you a heavy load on this server ? How many (concurent) users ?
On 10/18/06, Derek Wormdahl [EMAIL PROTECTED] wrote:
We initially started this project running on the Sun JVM but ran into an
issue with the JVM aborting when doing a
now when I do a thread dump it shows 540 threads but our available mem
on the server is still fine (and relatively unchanged since we started
the service) and the CPU is about 90% idle. The thread count just climbs.
We did hear about trying to set the LD_ASSUME_KERNEL parameter to 2.4.1
to use
From: Derek Wormdahl [mailto:[EMAIL PROTECTED]
Subject: max_threads issue blocked threads (*warning* long
thread dump attached)
We've been investigating an issue with a web application
that is causing us problems. We are seeing the Tomcat
server running out of available threads after
]
Subject: max_threads issue blocked threads (*warning* long
thread dump attached)
We've been investigating an issue with a web application
that is causing us problems. We are seeing the Tomcat
server running out of available threads after a few hours
of operation.
What happens if you run
threads
Is there a way to stop hung jk connector threads with out restarting
Tomcat?
I can see threads that are hanging from the Tomcat manager server
status page, but I can't kill them, only a server restart clears them.
Is there a better way?
Thanks,
Enrique
901 - 1000 of 1077 matches
Mail list logo
