Hi Tomcat users,
Can you share the jsp code of thread pool so
that I can analyse it
Thanks and Regards,
Deepak
On Wed, 6 Dec 2023, 8:46 pm Christopher Schultz, <
ch...@christopherschultz.net> wrote:
> William,
>
> On 12/5/23 14:39, William Crowe
William,
On 12/5/23 14:39, William Crowell wrote:
I should clarify the ask here…
I have some long running JDBC queries against Oracle, and I do not
want to tie up Tomcat’s web thread pool with them. I would only have
between 1-10 threads in this pool.
Executors aren't directly-accessib
You have to refer to it in your connector:
https://tomcat.apache.org/tomcat-10.0-doc/config/http.html
> -Original Message-
> From: William Crowell
> Sent: Tuesday, December 5, 2023 1:39 PM
> To: Tomcat Users List
> Subject: Re: Thread Pool Question
>
> I should
I should clarify the ask here…
I have some long running JDBC queries against Oracle, and I do not want to tie
up Tomcat’s web thread pool with them. I would only have between 1-10 threads
in this pool.
Regards,
William Crowell
This e-mail may contain information that is privileged or
If I create a separate thread pool in Tomcat’s server.xml like this:
Then how do I get a thread to assign any work to it?
Regards,
William Crowell
This e-mail may contain information that is privileged or confidential. If you
are not the intended recipient, please delete the e-mail and any
mcat.apache.org/tomcat-9.0-doc/config/executor.html
> >>
> >> Note that your current configuration has separate thread-pools, one for
> >> each . If you specify the "executor" configuration attribute,
> >> you can choose to share a single or have separate
t; wrote:
Jon,
On 12/6/21 10:28, Jonathan Yom-Tov wrote:
I have a single instance of Tomcat (version 9.0.54) in which the thread
count on a connector thread pool doesn't reduce despite most of the
threads
(198/200) being idle. If I understand correctly the default idle time
before a thread
tor.html
>
> Note that your current configuration has separate thread-pools, one for
> each . If you specify the "executor" configuration attribute,
> you can choose to share a single or have separate ones for
> each . If you want them separate, just define two of them and
28 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
Jon,
On 12/6/21 10:28, Jonathan Yom-Tov wrote:
I have a single instance of Tomcat (version 9.0.54) in which the thread
count on a connector thread pool doesn't reduce despite most of the
threads
(198/200) being idle. If I understand correc
rote:
> > I have a single instance of Tomcat (version 9.0.54) in which the thread
> > count on a connector thread pool doesn't reduce despite most of the
> threads
> > (198/200) being idle. If I understand correctly the default idle time
> > before a thread is reaped is 6
Jon,
On 12/6/21 10:28, Jonathan Yom-Tov wrote:
I have a single instance of Tomcat (version 9.0.54) in which the thread
count on a connector thread pool doesn't reduce despite most of the threads
(198/200) being idle. If I understand correctly the default idle time
before a thread is reap
hi,
I have a single instance of Tomcat (version 9.0.54) in which the thread
count on a connector thread pool doesn't reduce despite most of the threads
(198/200) being idle. If I understand correctly the default idle time
before a thread is reaped is 60 seconds, but this situation persist
t; 2016
>
> As Michael pointed-out, these all need to be upgraded, but they are not
> affecting your experience, here.
>
> > Observations:
> > After database failover, we noticed that HTTP thread pool size jumped
> > from 10 to 50. No. of busy threads jumped to 40 f
database failover, we noticed that HTTP thread pool size jumped
from 10 to 50. No. of busy threads jumped to 40 for a minute and then
came down to normal range(1-5). But thread pool size remained 50 for
the next one hour. When we collected the heap dump after one hour,
thread pool size jumped again to ~90
Hi Michael,
On Wed, Nov 11, 2020 at 6:03 PM Michael Osipov wrote:
>
> Am 2020-11-11 um 12:40 schrieb Suvendu Sekhar Mondal:
> > Hello Everyone,
> >
> > During database failover resiliency testing we noticed something
> > unusual which we still cannot explain. So, reaching out to the
> > community
Am 2020-11-11 um 12:40 schrieb Suvendu Sekhar Mondal:
Hello Everyone,
During database failover resiliency testing we noticed something
unusual which we still cannot explain. So, reaching out to the
community for help.
Application Setup:
AdoptOpenJDK 1.8.192, Tomcat 7.0.55, Apache httpd, Windows
failover, we noticed that HTTP thread pool size jumped
from 10 to 50. No. of busy threads jumped to 40 for a minute and then
came down to normal range(1-5). But thread pool size remained 50 for
the next one hour. When we collected the heap dump after one hour,
thread pool size jumped again to ~90
On 26/04/2019 06:25, Supun Abeysinghe wrote:
> Hi all,
>
>
> I am working on a project which tries to tune the Tomcat thread pool
> dynamically by looking at runtime characteristics in order to enhance the
> system performance. To get a better understanding, I have gone th
Hi all,
I am working on a project which tries to tune the Tomcat thread pool
dynamically by looking at runtime characteristics in order to enhance the
system performance. To get a better understanding, I have gone through the
Tomcat source code and found out that it uses ThreadPoolExecutor. It
your threadlocals
>>
>> On 5 February 2018 at 15:36, Shiva Kumar K R
>> wrote:
>>
>> > Hi,
>> >
>> > Component details:
>> > Tomcat = 8.5.24
>> > Java = 1.8
>> > OS = Ubuntu 16.04 LTS
>> >
>> > Is above to
n up the
> threadlocals..
> That is a problem by itself, you should always after a request have cleanup
> all your threadlocals
>
> On 5 February 2018 at 15:36, Shiva Kumar K R
> wrote:
>
> > Hi,
> >
> > Component details:
> > Tomcat = 8.5.24
> > Java =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shiva,
On 2/5/18 9:36 AM, Shiva Kumar K R wrote:
> Hi,
>
> Component details: Tomcat = 8.5.24 Java = 1.8 OS = Ubuntu 16.04
> LTS
>
> Is above tomcat uses thread pool to process requests out of the box
> without any expl
t = 8.5.24
> Java = 1.8
> OS = Ubuntu 16.04 LTS
>
> Is above tomcat uses thread pool to process requests out of the box without
> any explicit configuration of thread pool.
>
> I faced an issue while using threadlocal which was returning data stored in
> previous request
Hi,
Component details:
Tomcat = 8.5.24
Java = 1.8
OS = Ubuntu 16.04 LTS
Is above tomcat uses thread pool to process requests out of the box without
any explicit configuration of thread pool.
I faced an issue while using threadlocal which was returning data stored in
previous request instead of
Ouch! maxConnections! You're right. I failed to take account of it
correctly. Actually I was confused connections like threads (because of
maxThreads/Connections) and thought they release when their thread
releases :[ while a connection keeps alive until response and thread
pool is s
wing it out to get my
>> head around what is happening.
>>
>
> Sorry for bothering you,
>
> To examine if things going on either in JMeter or at the network, I
> tested same config (BIO,20,20,10) on Jetty. All 70 requests returned
> successfully and response time was ~
things going on either in JMeter or at the network
> level I don't understand. I had to resort to drawing it out to get my
> head around what is happening.
>
Sorry for bothering you,
To examine if things going on either in JMeter or at the network, I
tested same config (BIO,2
, 65 to 70 are
processed. It looks like there is some sort of timeout for acceptance or
rejection in the accept queue.
That explains the rejected requests.
The other question is why maxThreads is reported as it is.
The answer is that the thread pool never grows beyond its initial size
of 10. A req
ot; but I get!
>>
>> I have simulated a blocking operation by a sleep for 10 seconds. When my
>> servlet gets a request, it quickly starts an async and add further
>> processing to my own thread pool (container thread comes back to pool
>> quickly, right). My own thread pool
t;
>> Previously I also tested very low loads but again as you suggested I
>> tested following low load configuration and get even worse results!!
>> Tomcat successfully returns from request below 29th but fails 25
>> requests of 29th to 70th. However this time all fails are
to 70th. However this time all fails are "connection
> refuse" and there are not any "connection reset". Whilst the program
> output is "Container MAX used threads: 10" !!
>
> CONFIGURATION #2:
>
> Server.xml
> connectionTimeout=&qu
all fails are "connection
refuse" and there are not any "connection reset". Whilst the program
output is "Container MAX used threads: 10" !!
CONFIGURATION #2:
Server.xml
JMeter
Number of threads (users): 70
Ramp-Up period (in seconds): 35 (40 requests per 20 seconds
n by a sleep for 10 seconds. When my
> servlet gets a request, it quickly starts an async and add further
> processing to my own thread pool (container thread comes back to pool
> quickly, right). My own thread pool size is 310 which is greater than
> 304.3 (requests in 10 seconds) so never ful
> container max used threads count. It prints 187 for me which is lower
> than 200 (tomcat default pool size) so I should not get any "connection
> refuse" but I get!
>
> I have simulated a blocking operation by a sleep for 10 seconds. When my
> servlet gets a request
I should not get any "connection
refuse" but I get!
I have simulated a blocking operation by a sleep for 10 seconds. When my
servlet gets a request, it quickly starts an async and add further
processing to my own thread pool (container thread comes back to pool
quickly, right). My own th
On 17/08/2015 17:27, Wernersbach, Philip wrote:
> Hello All,
>
> We are developing a JDBC driver that implements the JDBC API. Our
> driver works and we can use it in servlets, but Tomcat doesn’t seem
> to know that the connections in the thread pool can be reused, so
>
Hello All,
We are developing a JDBC driver that implements the JDBC API. Our driver works
and we can use it in servlets, but Tomcat doesn’t seem to know that the
connections in the thread pool can be reused, so after all of the connection
slots in the thread pool are used, the servlets hang
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jeffrey,
On 3/10/14, 4:15 PM, Jeffrey Janner wrote:
>> -Original Message- From: Christopher Schultz
>> [mailto:ch...@christopherschultz.net] Sent: Monday, March 10,
>> 2014 11:22 AM To: Tomcat Users List Subject: Re: Execu
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Monday, March 10, 2014 11:22 AM
> To: Tomcat Users List
> Subject: Re: Executor thread pool
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> John,
>
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John,
On 3/10/14, 11:43 AM, John Smith wrote:
> How dumb am I being by not using an Executor with a named thread
> pool? Currently I just have a Connector in server.xml:
>
> protocol="org.apache.coyote.http11.
> From: John Smith [mailto:tomcat.ran...@gmail.com]
> Subject: Executor thread pool
> How dumb am I being by not using an Executor with a named thread pool?
> Currently I just have a Connector in server.xml:
> connectionTimeout="2"
>
How dumb am I being by not using an Executor with a named thread pool?
Currently I just have a Connector in server.xml:
Assuming ~2000 simultaneous connections. Tomcat 7.0.42. RHEL6.
Best,
John
On Tue, Oct 8, 2013 at 5:42 AM, Daniel Mikusa wrote:
> On Oct 7, 2013, at 11:14 PM, John Rellis wrote:
>
>> Hi,
>>
>> Tomcat : 7.0.33
>> Java : 6
>> JDBC Pool : 1.0.9.3
>> Grails : 1.3.9
>>
>> We are running a grails app that is using the
On Oct 7, 2013, at 11:14 PM, John Rellis wrote:
> Hi,
>
> Tomcat : 7.0.33
> Java : 6
> JDBC Pool : 1.0.9.3
> Grails : 1.3.9
>
> We are running a grails app that is using the tomcat JDBC thread pool, what
> we are seeing is the idle connections falling below minI
Hi,
Tomcat : 7.0.33
Java : 6
JDBC Pool : 1.0.9.3
Grails : 1.3.9
We are running a grails app that is using the tomcat JDBC thread pool, what
we are seeing is the idle connections falling below minIdle and then
continuously heading towards zero over the course of a few hours.
I think I understand
nswer.
>>>>
>>>> I'd like to use the Tomcat 7 thread pool as worker threads for
>>>> Quartz Scheduler.
>
> Why would you want to dip-into the request-processor pool instead of
> maintaining a separate one?
>
>> To conserve shared resources
lt in DB connection pool / the DBCP is often a shared
resource.
Hmm. I think perhaps I can configure a common thread pool and expose it via
JNDI to the web apps.
http://tomcat.apache.org/tomcat-7.0-doc/jndi-resources-howto.html#Generic_JavaBean_Resources
Oz
>
>> Is there a way to a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oguz,
On 6/14/12 6:24 AM, Oguz Kologlu wrote:
> I've seen this question bounce around some threads but there's
> really no good answer.
>
> I'd like to use the Tomcat 7 thread pool as worker threads for
> Quartz Schedul
Hi All,
I've seen this question bounce around some threads but there's really no good
answer.
I'd like to use the Tomcat 7 thread pool as worker threads for Quartz
Scheduler.
Is there a way to access the thread pool from a web app? Any other suggestio
Forgive me if my first message was unclear.
I have an executor and an AJP connector set up.
When I watch it with psi-Probe, I can see that it is indeed killing idle
threads as I expect it to. What I am not seeing is the minSpareThreads
attribute being honored as I expect it to, though it ma
In Tomcat 6, the default thread pool ignores minSpareThreads, but if you use
and then From: llow...@oreillyauto.com
> To: users@tomcat.apache.org
> Sent: Wednesday, April 4, 2012 7:50:24 AM
> Subject: Tomcat6 thread pool questions
>
>
> Greetings,
>
> I was wondering
On 04/04/2012 14:50, llow...@oreillyauto.com wrote:
>
> Greetings,
>
> I was wondering if someone could help me understand how the threadpools are
> handled in tomcat6. I know that a lot of the functionality was moved to
> executors.
>
> I set one up and using psi-Probe I could see that it was i
Greetings,
I was wondering if someone could help me understand how the threadpools are
handled in tomcat6. I know that a lot of the functionality was moved to
executors.
I set one up and using psi-Probe I could see that it was indeed killing off
threads as I expected. However, the minSpareThread
Hi,
I'm using Tomcat 7.0.20.
I'm writing java code for automated Thread utilization monitoring and alert
system.
I'm struggling to find the Mbean descriptor for Mbeans under
Catalina.ThreadPool.
Can anyone provide any reference?
The big question I've is what the currentThreadCount indicates
On 27/06/2011 11:23, uri unger wrote:
> hi,
>
> i'm using tomcat 7.0.16.
> i'm trying to define a thread pool using an Executor/Connector elements as
> follows:
>
>maxThreads="6500" minSpareThreads="4"/>
>
hi,
i'm using tomcat 7.0.16.
i'm trying to define a thread pool using an Executor/Connector elements as
follows:
I have also disabled the access log Valve.
Other than these configuration changes, my server.xml file is identical to
the default one bundled in the official release
> From: CBy [mailto:tom...@byrman.demon.nl]
> Subject: Re: [OT] Question on Executor (thread pool)
>
> I thought it was pretty common to share precious resources across web
> apps. Isn't database connection pooling often implemented this way?
Not in my experience - you wa
On 8-3-2010 17:07, Caldarale, Charles R wrote:
From: CBy [mailto:tom...@byrman.demon.nl]
Subject: Re: [OT] Question on Executor (thread pool)
I am still curious though on when and how to use Tomcat's Executor. I
someone could provide me with a nice example, I would be most gra
> From: CBy [mailto:tom...@byrman.demon.nl]
> Subject: Re: [OT] Question on Executor (thread pool)
>
> I am still curious though on when and how to use Tomcat's Executor. I
> someone could provide me with a nice example, I would be most grateful.
Tomcat's thread pools
he maximum number of instances that can run
concurrently, it uses a (custom) thread pool.
Are you on Java 1.5+? (If not, you should be).
If you are, you can use one of the fine implementations of executors in
java.util.concurrent, such as ThreadPoolExecutor.
Now that I have to
develop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
CBy,
On 3/8/2010 7:03 AM, CBy wrote:
> My web service wraps a command-line application that is rather resource
> demanding. To manage the maximum number of instances that can run
> concurrently, it uses a (custom) thread pool.
Are you on
Hi,
My web service wraps a command-line application that is rather resource
demanding. To manage the maximum number of instances that can run
concurrently, it uses a (custom) thread pool. This all works fine, but
my current thread pool is local to my service. Now that I have to
develop
amed http-8080-exec-1, http-8080-exec-2, etc. But now after two days, I
cannot see those threads anymore. It currently has http-8080-exec-480,
http-8080-exec-481, etc. How can a thread be removed from a thread pool?
I
can imagine a thread being suspended or waiting on a busy
or. In the first few hours of Tomcat startup, threads
> were
> > named http-8080-exec-1, http-8080-exec-2, etc. But now after two days, I
> > cannot see those threads anymore. It currently has http-8080-exec-480,
> > http-8080-exec-481, etc. How can a thread be removed from
ose threads anymore. It currently has http-8080-exec-480,
> http-8080-exec-481, etc. How can a thread be removed from a thread pool? I
> can imagine a thread being suspended or waiting on a busy resource, but how
> can it be removed?
Executors use dynamically sized thread pools. A thread can b
80-exec-480,
http-8080-exec-481, etc. How can a thread be removed from a thread pool? I
can imagine a thread being suspended or waiting on a busy resource, but how
can it be removed?
Mohsen
On Sat, Nov 14, 2009 at 8:55 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> >
> From: Mohsen Saboorian [mailto:mohs...@gmail.com]
> Subject: Re: Dedicated Thread Pool
>
> Chuck, how can I bind the new to a different webapp
> directory?
You can't, unless you create an additional and - which is
likely more trouble than it's worth. Just us
Thanks for the answers.
Chuck, how can I bind the new to a different webapp directory?
Mohsen
On Sat, Nov 14, 2009 at 8:26 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Mohsen Saboorian [mailto:mohs...@gmail.com]
> > Subject: Dedicated Thread Po
Mohsen Saboorian wrote:
I have a web application in Tomcat 6 which goes out of thread (thread
starvation) after working some hours. Now I want to install a monitoring
tool which is a webapp itself installed inside tomcat webapp folder. Is this
possible to devote a special threadpool to one web ap
> From: Mohsen Saboorian [mailto:mohs...@gmail.com]
> Subject: Dedicated Thread Pool
>
> Is this possible to devote a special threadpool to one web
> application, so that I can investigate what's going on
> through that monitoring app?
Not directly. However, you can
Hi,
I have a web application in Tomcat 6 which goes out of thread (thread
starvation) after working some hours. Now I want to install a monitoring
tool which is a webapp itself installed inside tomcat webapp folder. Is this
possible to devote a special threadpool to one web application, so that I
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: splitting thread pool
>
> The only way I know of to do this is with separate connectors:
One thing that hasn't been discussed is whether HTTP keep-alives are involved.
If so, then using the NI
: Monday, June 29, 2009 10:49:06 AM
Subject: Re: splitting thread pool
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Prashant,
On 6/29/2009 1:12 AM, prashant sharma wrote:
> Is there any way to configure my web application such that I have a
> separate quota of threads for webpage access
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Prashant,
On 6/29/2009 1:12 AM, prashant sharma wrote:
> Is there any way to configure my web application such that I have a
> separate quota of threads for webpage access and a separate quota for
> other types of accesses like webservice requests?
T
response Ronald!
Won't a filter be a part of the thread pool? I mean every incoming request would create a new thread and filter would be invoked on this new thread ...right?
The solution that I am looking for is to partition the thread pool into 2 parts
One that serves the webpage req
Thanks for your response Ronald!
Won't a filter be a part of the thread pool? I mean every incoming request
would create a new thread and filter would be invoked on this new thread
...right?
The solution that I am looking for is to partition the thread pool into 2 parts
One that serve
You can create a filter or run on separate Tomcat instances.
NB: You are not solving the cause, but the effect. You don't have enough
threads or cpu-power to handle the total load.
Ronald.
Op maandag, 29 juni 2009 07:12 schreef prashant sharma :>
Hi,
I have the following attributes in the
Hi,
I have the following attributes in the "server.xml" file:
The web application that I am working on exposes many webservices, which are
invoked from other applications. The problem I am facing is that when my
application gets a lot of webservice requests, it reaches the limit of
"maxThrea
Dan Armbrust wrote:
> Is there a way to get the values of variables from the server.xml file
> from a webapp running within tomcat?
JMX.
> Specifically, my webapp would like to know what the current value of
> the Connector acceptCount.
>
> Even more specifically, my webapp is serving pages, and
Is there a way to get the values of variables from the server.xml file
from a webapp running within tomcat?
Specifically, my webapp would like to know what the current value of
the Connector acceptCount.
Even more specifically, my webapp is serving pages, and answering SOAP
requests. I need to p
> From: André Warnier [mailto:[EMAIL PROTECTED]
> Subject: Re: Tomcat thread pool question
>
> So it has nothing to do directly with the threads.
Only in determining how many requests can be accepted by Tomcat before going on
the limited TCP/IP queue and subsequent requests being re
Caldarale, Charles R wrote:
From: André Warnier [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat thread pool question
So we have a Tomcat, which somehow has a "pool of database
connections" ready to be lent to webapps.
In this particular case, the db connection pool is managed by Hibe
> From: André Warnier [mailto:[EMAIL PROTECTED]
> Subject: Re: Tomcat thread pool question
>
> So we have a Tomcat, which somehow has a "pool of database
> connections" ready to be lent to webapps.
In this particular case, the db connection pool is managed by Hibernate, n
Possibly [OT], and just disregard if so.
I am just trying to follow this thread and to understand, from my very
superficial and elementary knowledge of things Java and Tomcat.
So we have a Tomcat, which somehow has a "pool of database connections"
ready to be lent to webapps.
And we have a
not necessarily endorse content contained within this transmission.
> Date: Wed, 10 Dec 2008 17:15:39 -0500
> From: [EMAIL PROTECTED]
> To: users@tomcat.apache.org
> Subject: Re: Tomcat thread pool question
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Pe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
Christopher Schultz wrote:
> So, unless you have maxActive == dbcp size, you're screwed.
Er, that should be maxActive == maxThreads.
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http
ped schrieb am 10.12.2008 um 10:33:23 (-0800):
> > The Tomcat thread pool is finite; we'll call the maxThread value T.
> > Likewise, the db connection pool is finite, and we'll call its size
> > D. The client makes some number of requests that are not committed,
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ped,
ped wrote:
> I would think that I should be able to increase the number of threads
> available to Tomcat to prevent this problem (I'm not saying that is the
> correct solution to my problem - I fully understand that our design is the
> root of th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ped,
ped wrote:
> If I execute the loop N-1 times, I have no problems - I can execute my loop
> over and over. I can verify that I am not leaking connections (I have a
> monitor thread that displays the number of active connections).
I'm probably joi
>The Tomcat thread pool is finite; we'll call the maxThread value T.
Likewise, the db connection pool is finite, and we'll call its size D. The
client makes some number of requests that are not committed, which we'll
label R. Anytime R > T + D, you're stuck.
Yes -
> From: ped [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat thread pool question
>
> So that implies that Tomcat only supports a max of 3 threads...
Obviously untrue, since the default is 200.
> I uncommented:
> maxThreads="150" minSpareThreads="1"/&
able to increase the number of threads
available to Tomcat to prevent this problem (I'm not saying that is the
correct solution to my problem - I fully understand that our design is the
root of this problem).
--
View this message in context:
http://www.nabble.com/Tomcat-thread-
> From: ped [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat thread pool question
>
> Perhaps there is a subtle bug here, or misconfiguration on
> my part
It's not subtle - it's blatant. The db connection pool is exhausted, all of
the Tomcat threads are waiting for
e pool
- but that should just cause poor performance, rather than non-functional
code).
--
View this message in context:
http://www.nabble.com/Tomcat-thread-pool-question-tp20915752p20937425.html
Sent from the Tomcat - User maili
> From: ped [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat thread pool question
>
> I believe that all of the code below (except the top 4 call
> frames) are coyote and catalina code.
It's the top frames that are critical, of course, since they show where the
thread is stuck
t;
> - Chuck
>
>
--
View this message in context:
http://www.nabble.com/Tomcat-thread-pool-question-tp20915752p20935709.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAI
> From: ped [mailto:[EMAIL PROTECTED]
> Subject: Re: Tomcat thread pool question
>
> No DB connections will be freed because the requests from the
> client that are trying to perform commits (thereby freeing a DB
> connection) are not being processed by Tomcat.
Tomcat doesn&
request? Is the connection being closed or anything?
>
> Is it possible to reproduce the error by making a Servlet that simulates
> blocking on a database connection by sleeping for N seconds?
>
>
>
--
View this message in context:
http://www.nabble.com/Tomcat-thread-po
Hi Peter,
ped wrote:
The problem occurs if I set max threads to N and execute the above loop N+1
or more times (where N is a small number like 3 or 4). I see Tomcat threads
sitting in c3p0 code waiting for a connection. There is no thread handling
the incoming commit calls (step 3 above). The in
me to believe that Tomcat is
honoring the c3p0 max threads.
Any help or insight is appreciated.
--
View this message in context:
http://www.nabble.com/Tomcat-thread-pool-question-tp20915752p20915752.html
Sent from the Tomcat - User mailing list archive at Nabbl
1 - 100 of 136 matches
Mail list logo
