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 Crowell wrote:
> > I shoul
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-accessible by
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 conf
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
> 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,
> > which we'll label R. Anytime R
-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
that's my understanding of the problem. But as I change D (my db
connection pool size) and R, Tomcat's maxThread value (T) seems to be very
small (1 or 2). That surprised me, and led me to think something else was
going on here.
--
View this message in context:
http://www.na
> 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
25 matches
Mail list logo
