2. you can use kill -3 command to dump the thread stack and execute the same
command few seconds later. You obtain two stack trace that you can compare
to identify the potential source of inativity.
-Message d'origine-
De : Matt Robinson [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 8
://www.yoavshapira.com
-Original Message-
From: Arnab Chakravarty [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 10:50 PM
To: Tomcat Users List
Subject: RE: Threads issues in Tomcat 5.0.28
Hey,
I see your problem similar to mine some time in the past. What you need
to is the following
Chakravarty
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 10:50 PM
To: Tomcat Users List
Subject: RE: Threads issues in Tomcat 5.0.28
Hey,
I see your problem similar to mine some time in the
past. What you need
to is the following:
- Lower the number of threads and keep it close
-
From: Matt Robinson [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 09, 2004 2:29 AM
To: Tomcat Users List
Subject: RE: Threads issues in Tomcat 5.0.28
Hi Yoav,
Thanks for the response I will be sure to include my
Thread dump. Meanwhile it sames that AJP13 in Tomcat5
has no parameters
-Original Message-
From: Matt Robinson [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 09, 2004 2:29 AM
To: Tomcat Users List
Subject: RE: Threads issues in Tomcat 5.0.28
Hi Yoav,
Thanks for the response I will be sure to include my
Thread dump. Meanwhile it sames that AJP13 in Tomcat5
has
Hey,
I see your problem similar to mine some time in the past. What you need
to is the following:
- Lower the number of threads and keep it close to 120-150 threads.
- Are you using a database, if yes, check if the DB connection pool is
the bottleneck
- Yes, you can find what the 200 threads are
