Re: AW: ThreadPool: Pool exhausted with 100 threads
Hi Matt,
Another option is this. If you do 'kill -QUIT ' on Linux or ctrl-break on
Windows in the dosbox running Java (if this is how you run Tomcat) it will print all
stacktraces of all threads. Very helpfull to track down lost Threads.
And another 'trick' I use is the following filter.
doFilter(request, response, chain) {
Thread currThr = Thread.currentThread();
String oldName = currThr.getName();
try {
currThr.setName(request.getRequestURI());
chain.doFilter(request, response);
} finally {
currThr.setName(oldName);
}
}
The jsp with the threadlist than displays the URL's which are being processed. Very
helpfull. But as far as I now Tomcat 3 doesn't support filters.
Greetings,
Ronald.
On Tue Sep 07 23:18:39 CEST 2004 Matt Robinson <[EMAIL PROTECTED]> wrote:
Ronald, Thanks this is quite helpful - using your jsp
I can see where we hit 100 threads and Tomcat freezes.
As I monitor our systems the number of threads slowly
grows until 100 is reached. The threads I see when
monitoring (using your JSP page) are not closed --
instead they seem to hang out until the 100 mark is
reached (at which point we have to restart Tomcat).
In effort to avoid this, it looks like we'll be
switching to 5.0.28 after some initial testing. Any
further suggestions more than welcome
Thanks again,
Matt
--- Ronald Klop <[EMAIL PROTECTED]> wrote:
>So, this is an error from the ThreadPool and not
>from java or the OS. The errors I got we're errors
>from the OS because of a limited nr of threads per
>process. There are issues with the ThreadPool solved
>in both 4 and 5 (see changelogs), so maybe this will
>be solved for you also.
>
>At my work I use a jsp which I will attach. It shows
>all running threads and threadgroups by there name.
>It gave me some usefull insight in the inner
>workings of Tomcat.
>
>Ronald.
>
>
>
>On Tue Sep 07 07:08:10 CEST 2004 Matt Robinson
><[EMAIL PROTECTED]> wrote:
>>Ronald,
>>
>>The exact error message is "ThreadPool: Pool
>exhausted
>>with 100 threads", so I assume we have 100 threads
>>running -- once this error message appears Tomcat
>>stops responding until it is restarted. Is there a
>>simple way to check # of threads in use by Tomcat
>at
>>any given time?
>>
>>We are running Tomcat 3.2.4 and J2SE 1.4 on
>Windows
>>2000. Based on yours and other feedback, we plan
>on
>>upgrading to 4.x or 5.0 but not sure which is the
>>right choice.
>>
>>Thanks,
>>Matt
>>
>>--- Ronald Klop <[EMAIL PROTECTED]>
>wrote:
>>
>>>On Mon Sep 06 00:40:14 CEST 2004 Matt Robinson
>>><[EMAIL PROTECTED]> wrote:
>>>>Steffen,
>>>>
>>>>Many thanks for the response. The reason we
>stuck
>>>with
>>>>3.2.4 was because of stability. However, as we
>>>have
>>>>become more successful our systems have been
>>>receiving
>>>>heavier loads and thus, the Threadpool exhausted
>>>>problem.
>>>>
>>>>Regarding stability/reliability (uptime is a
>>>greater
>>>>concern for us than performance), would you
>>>recommend
>>>>5.0 over 4.x or vice versa?
>>>>
>>>>Also curious if anyone has experienced thread
>pool
>>>>problems (or successes) with medium to high load
>>>>systems under either 4.x or 5.0.
>>>>
>>>>Thanks again,
>>>>Matt
>>>>
>>>
>>>
>>>How many threads do you have when it is exhausted
>>>and what is the error message you get?
>>>We are running Tomcat 5 with about hundred
>threads
>>>quite ok here. Tomcat 5 is much more efficient,
>so
>>>it can help you to try it out.
>>>
>>>Ronald.
>>>
>>>
>>>
>>
>>
>>
>>
>>__
>>Do you Yahoo!?
>>Read only the mail you want - Yahoo! Mail
>SpamGuard.
>>http://promotions.yahoo.com/new_mail
>>
>>
>
-
>>To unsubscribe, e-mail:
>[EMAIL PROTECTED]
>>For additional commands, e-mail:
>[EMAIL PROTECTED]
>>
>
>><%@ page
>info = "$Id: threads.jsp,v 1.2 2003/05/26 19:24:55
>ronald Exp $"
>import = "
>java.util.Calendar,
>java.util.TimeZone
>"
>%>
><%!
>class Group {
>JspWriter out;
>Group(JspWriter out) {
>this.out = out;
>}
>void print(ThreadGroup tg, String prefix) throws
>java.io.IOException {
>int i;
>out.println(prefix + "G " + tg
Re: AW: ThreadPool: Pool exhausted with 100 threads
Hi,
well there is a long time since I stoped using 3.* but if I remember it correctly you can add threads to the threadpool on the
Http10Connector settings in your server.xml (or if you are using AJPConnector you should be able to add it there).
Maybe that would be a quick fix, to say, double the maxThreads parameter.
see the documentation for 3.3:
http://jakarta.apache.org/tomcat/tomcat-3.3-doc/serverxml.html
for more settings.
hope it helps,
-reynir
Matt Robinson wrote:
Ronald, Thanks this is quite helpful - using your jsp
I can see where we hit 100 threads and Tomcat freezes.
As I monitor our systems the number of threads slowly
grows until 100 is reached. The threads I see when
monitoring (using your JSP page) are not closed --
instead they seem to hang out until the 100 mark is
reached (at which point we have to restart Tomcat).
In effort to avoid this, it looks like we'll be
switching to 5.0.28 after some initial testing. Any
further suggestions more than welcome
Thanks again,
Matt
--- Ronald Klop <[EMAIL PROTECTED]> wrote:
So, this is an error from the ThreadPool and not
from java or the OS. The errors I got we're errors
from the OS because of a limited nr of threads per
process. There are issues with the ThreadPool solved
in both 4 and 5 (see changelogs), so maybe this will
be solved for you also.
At my work I use a jsp which I will attach. It shows
all running threads and threadgroups by there name.
It gave me some usefull insight in the inner
workings of Tomcat.
Ronald.
On Tue Sep 07 07:08:10 CEST 2004 Matt Robinson
<[EMAIL PROTECTED]> wrote:
Ronald,
The exact error message is "ThreadPool: Pool
exhausted
with 100 threads", so I assume we have 100 threads
running -- once this error message appears Tomcat
stops responding until it is restarted. Is there a
simple way to check # of threads in use by Tomcat
at
any given time?
We are running Tomcat 3.2.4 and J2SE 1.4 on
Windows
2000. Based on yours and other feedback, we plan
on
upgrading to 4.x or 5.0 but not sure which is the
right choice.
Thanks,
Matt
--- Ronald Klop <[EMAIL PROTECTED]>
wrote:
On Mon Sep 06 00:40:14 CEST 2004 Matt Robinson
<[EMAIL PROTECTED]> wrote:
Steffen,
Many thanks for the response. The reason we
stuck
with
3.2.4 was because of stability. However, as we
have
become more successful our systems have been
receiving
heavier loads and thus, the Threadpool exhausted
problem.
Regarding stability/reliability (uptime is a
greater
concern for us than performance), would you
recommend
5.0 over 4.x or vice versa?
Also curious if anyone has experienced thread
pool
problems (or successes) with medium to high load
systems under either 4.x or 5.0.
Thanks again,
Matt
How many threads do you have when it is exhausted
and what is the error message you get?
We are running Tomcat 5 with about hundred
threads
quite ok here. Tomcat 5 is much more efficient,
so
it can help you to try it out.
Ronald.
__
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail
SpamGuard.
http://promotions.yahoo.com/new_mail
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
<%@ page
info = "$Id: threads.jsp,v 1.2 2003/05/26 19:24:55
ronald Exp $"
import = "
java.util.Calendar,
java.util.TimeZone
"
%>
<%!
class Group {
JspWriter out;
Group(JspWriter out) {
this.out = out;
}
void print(ThreadGroup tg, String prefix) throws
java.io.IOException {
int i;
out.println(prefix + "G " + tg.getName());
ThreadGroup[] tga = new
ThreadGroup[tg.activeGroupCount()];
int nr = tg.enumerate(tga, false);
for(i = 0; i < nr; i++) {
this.print(tga[i], prefix + "\t");
}
Thread[] ta = new Thread[tg.activeCount()];
nr = tg.enumerate(ta, false);
String[] names = new String[nr];
for(i = 0; i < names.length; i++) {
names[i] = ta[i].getName();
}
java.util.Arrays.sort(names);
for(i = 0; i < nr; i++) {
out.println(prefix + "T " + names[i]);
}
}
}
%>
<%@ include file="/pub/exec/baseDHTML.jspf" %>
Threads -
<%=request.getServerName()%>
<%
java.util.Date now =
Calendar.getInstance(TimeZone.getTimeZone("Europe/Amsterdam")).getTime();
%>
Time: <%=now.toString()%>
<%
Thread c
Re: AW: ThreadPool: Pool exhausted with 100 threads
Ronald, Thanks this is quite helpful - using your jsp
I can see where we hit 100 threads and Tomcat freezes.
As I monitor our systems the number of threads slowly
grows until 100 is reached. The threads I see when
monitoring (using your JSP page) are not closed --
instead they seem to hang out until the 100 mark is
reached (at which point we have to restart Tomcat).
In effort to avoid this, it looks like we'll be
switching to 5.0.28 after some initial testing. Any
further suggestions more than welcome
Thanks again,
Matt
--- Ronald Klop <[EMAIL PROTECTED]> wrote:
> So, this is an error from the ThreadPool and not
> from java or the OS. The errors I got we're errors
> from the OS because of a limited nr of threads per
> process. There are issues with the ThreadPool solved
> in both 4 and 5 (see changelogs), so maybe this will
> be solved for you also.
>
> At my work I use a jsp which I will attach. It shows
> all running threads and threadgroups by there name.
> It gave me some usefull insight in the inner
> workings of Tomcat.
>
> Ronald.
>
>
>
> On Tue Sep 07 07:08:10 CEST 2004 Matt Robinson
> <[EMAIL PROTECTED]> wrote:
> > Ronald,
> >
> > The exact error message is "ThreadPool: Pool
> exhausted
> > with 100 threads", so I assume we have 100 threads
> > running -- once this error message appears Tomcat
> > stops responding until it is restarted. Is there a
> > simple way to check # of threads in use by Tomcat
> at
> > any given time?
> >
> > We are running Tomcat 3.2.4 and J2SE 1.4 on
> Windows
> > 2000. Based on yours and other feedback, we plan
> on
> > upgrading to 4.x or 5.0 but not sure which is the
> > right choice.
> >
> > Thanks,
> > Matt
> >
> > --- Ronald Klop <[EMAIL PROTECTED]>
> wrote:
> >
> > >On Mon Sep 06 00:40:14 CEST 2004 Matt Robinson
> > ><[EMAIL PROTECTED]> wrote:
> > >>Steffen,
> > >>
> > >>Many thanks for the response. The reason we
> stuck
> > >with
> > >>3.2.4 was because of stability. However, as we
> > >have
> > >>become more successful our systems have been
> > >receiving
> > >>heavier loads and thus, the Threadpool exhausted
> > >>problem.
> > >>
> > >>Regarding stability/reliability (uptime is a
> > >greater
> > >>concern for us than performance), would you
> > >recommend
> > >>5.0 over 4.x or vice versa?
> > >>
> > >>Also curious if anyone has experienced thread
> pool
> > >>problems (or successes) with medium to high load
> > >>systems under either 4.x or 5.0.
> > >>
> > >>Thanks again,
> > >>Matt
> > >>
> > >
> > >
> > >How many threads do you have when it is exhausted
> > >and what is the error message you get?
> > >We are running Tomcat 5 with about hundred
> threads
> > >quite ok here. Tomcat 5 is much more efficient,
> so
> > >it can help you to try it out.
> > >
> > >Ronald.
> > >
> > >
> > >
> >
> >
> >
> >
> > __
> > Do you Yahoo!?
> > Read only the mail you want - Yahoo! Mail
> SpamGuard.
> > http://promotions.yahoo.com/new_mail
> >
> >
>
-
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail:
> [EMAIL PROTECTED]
> >
>
> > <%@ page
> info = "$Id: threads.jsp,v 1.2 2003/05/26 19:24:55
> ronald Exp $"
> import = "
> java.util.Calendar,
> java.util.TimeZone
> "
> %>
> <%!
> class Group {
> JspWriter out;
> Group(JspWriter out) {
> this.out = out;
> }
> void print(ThreadGroup tg, String prefix) throws
> java.io.IOException {
> int i;
> out.println(prefix + "G " + tg.getName());
> ThreadGroup[] tga = new
> ThreadGroup[tg.activeGroupCount()];
> int nr = tg.enumerate(tga, false);
> for(i = 0; i < nr; i++) {
> this.print(tga[i], prefix + "\t");
> }
> Thread[] ta = new Thread[tg.activeCount()];
> nr = tg.enumerate(ta, false);
>
Re: AW: ThreadPool: Pool exhausted with 100 threads
So, this is an error from the ThreadPool and not from java or the OS. The errors I got we're errors from the OS because of a limited nr of threads per process. There are issues with the ThreadPool solved in both 4 and 5 (see changelogs), so maybe this will be solved for you also.
At my work I use a jsp which I will attach. It shows all running threads and threadgroups by there name. It gave me some usefull insight in the inner workings of Tomcat.
Ronald.
On Tue Sep 07 07:08:10 CEST 2004 Matt Robinson <[EMAIL PROTECTED]> wrote:
Ronald,The exact error message is "ThreadPool: Pool exhaustedwith 100 threads", so I assume we have 100 threadsrunning -- once this error message appears Tomcatstops responding until it is restarted. Is there asimple way to check # of threads in use by Tomcat atany given time?We are running Tomcat 3.2.4 and J2SE 1.4 on Windows2000. Based on yours and other feedback, we plan onupgrading to 4.x or 5.0 but not sure which is theright choice.Thanks,Matt--- Ronald Klop <[EMAIL PROTECTED]> wrote:> On Mon Sep 06 00:40:14 CEST 2004 Matt Robinson> <[EMAIL PROTECTED]> wrote:> > Steffen,> > > > Many thanks for the response. The reason we stuck> with> > 3.2.4 was because of stability. However, as we> have> > become more successful our systems have been> receiving> > heavier loads and thus, the Threadpool exhausted> > problem.> > > > Regarding stability/reliability (uptime is a> greater> > concern for us than performance), would you> recommend> > 5.0 over 4.x or vice versa? > > > > Also curious if anyone has experienced thread pool> > problems (or successes) with medium to high load> > systems under either 4.x or 5.0.> > > > Thanks again,> > Matt> > > > > How many threads do you have when it is exhausted> and what is the error message you get?> We are running Tomcat 5 with about hundred threads> quite ok here. Tomcat 5 is much more efficient, so> it can help you to try it out.> > Ronald.> > > __Do you Yahoo!?Read only the mail you want - Yahoo! Mail SpamGuard.http://promotions.yahoo.com/new_mail -To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]<%@ page
info = "$Id: threads.jsp,v 1.2 2003/05/26 19:24:55 ronald Exp $"
import = "
java.util.Calendar,
java.util.TimeZone
"
%>
<%!
class Group {
JspWriter out;
Group(JspWriter out) {
this.out = out;
}
void print(ThreadGroup tg, String prefix) throws java.io.IOException {
int i;
out.println(prefix + "G " + tg.getName());
ThreadGroup[] tga = new ThreadGroup[tg.activeGroupCount()];
int nr = tg.enumerate(tga, false);
for(i = 0; i < nr; i++) {
this.print(tga[i], prefix + "\t");
}
Thread[] ta = new Thread[tg.activeCount()];
nr = tg.enumerate(ta, false);
String[] names = new String[nr];
for(i = 0; i < names.length; i++) {
names[i] = ta[i].getName();
}
java.util.Arrays.sort(names);
for(i = 0; i < nr; i++) {
out.println(prefix + "T " + names[i]);
}
}
}
%>
<%@ include file="/pub/exec/baseDHTML.jspf" %>
Threads - <%=request.getServerName()%>
<%
java.util.Date now =
Calendar.getInstance(TimeZone.getTimeZone("Europe/Amsterdam")).getTime();
%>
Time: <%=now.toString()%>
<%
Thread current = Thread.currentThread();
ThreadGroup tg = current.getThreadGroup();
while(tg.getParent() != null) {
tg = tg.getParent();
}
Group g = new Group(out);
g.print(tg, "");
%>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: ThreadPool: Pool exhausted with 100 threads
Ronald, The exact error message is "ThreadPool: Pool exhausted with 100 threads", so I assume we have 100 threads running -- once this error message appears Tomcat stops responding until it is restarted. Is there a simple way to check # of threads in use by Tomcat at any given time? We are running Tomcat 3.2.4 and J2SE 1.4 on Windows 2000. Based on yours and other feedback, we plan on upgrading to 4.x or 5.0 but not sure which is the right choice. Thanks, Matt --- Ronald Klop <[EMAIL PROTECTED]> wrote: > On Mon Sep 06 00:40:14 CEST 2004 Matt Robinson > <[EMAIL PROTECTED]> wrote: > > Steffen, > > > > Many thanks for the response. The reason we stuck > with > > 3.2.4 was because of stability. However, as we > have > > become more successful our systems have been > receiving > > heavier loads and thus, the Threadpool exhausted > > problem. > > > > Regarding stability/reliability (uptime is a > greater > > concern for us than performance), would you > recommend > > 5.0 over 4.x or vice versa? > > > > Also curious if anyone has experienced thread pool > > problems (or successes) with medium to high load > > systems under either 4.x or 5.0. > > > > Thanks again, > > Matt > > > > > How many threads do you have when it is exhausted > and what is the error message you get? > We are running Tomcat 5 with about hundred threads > quite ok here. Tomcat 5 is much more efficient, so > it can help you to try it out. > > Ronald. > > > __ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: ThreadPool: Pool exhausted with 100 threads
On Mon Sep 06 00:40:14 CEST 2004 Matt Robinson <[EMAIL PROTECTED]> wrote: Steffen, Many thanks for the response. The reason we stuck with 3.2.4 was because of stability. However, as we have become more successful our systems have been receiving heavier loads and thus, the Threadpool exhausted problem. Regarding stability/reliability (uptime is a greater concern for us than performance), would you recommend 5.0 over 4.x or vice versa? Also curious if anyone has experienced thread pool problems (or successes) with medium to high load systems under either 4.x or 5.0. Thanks again, Matt What OS are you running? Last week I tweaked glibc of debian 3.0 to support more threads, because the defaults are quite low for heavily threaded programs. Ronald.
Re: AW: ThreadPool: Pool exhausted with 100 threads
On Mon Sep 06 00:40:14 CEST 2004 Matt Robinson <[EMAIL PROTECTED]> wrote: Steffen, Many thanks for the response. The reason we stuck with 3.2.4 was because of stability. However, as we have become more successful our systems have been receiving heavier loads and thus, the Threadpool exhausted problem. Regarding stability/reliability (uptime is a greater concern for us than performance), would you recommend 5.0 over 4.x or vice versa? Also curious if anyone has experienced thread pool problems (or successes) with medium to high load systems under either 4.x or 5.0. Thanks again, Matt How many threads do you have when it is exhausted and what is the error message you get? We are running Tomcat 5 with about hundred threads quite ok here. Tomcat 5 is much more efficient, so it can help you to try it out. Ronald.
Re: AW: ThreadPool: Pool exhausted with 100 threads
Steffen, Many thanks for the response. The reason we stuck with 3.2.4 was because of stability. However, as we have become more successful our systems have been receiving heavier loads and thus, the Threadpool exhausted problem. Regarding stability/reliability (uptime is a greater concern for us than performance), would you recommend 5.0 over 4.x or vice versa? Also curious if anyone has experienced thread pool problems (or successes) with medium to high load systems under either 4.x or 5.0. Thanks again, Matt --- SH Solutions <[EMAIL PROTECTED]> wrote: > Hi > > > Has anyone been able to solve or work around this > problem under Tomcat > 3.2.1? > > Any reasaon for this? > There is hardly anyone who can help you with 3.x. > 3.x is of stone age, 4.0.x is already very old, > 4.1.x is maintained but also > not current, and 5.0 is already stable for a while. > Even 5.5 is available but in early stages. > > If possible, try to upgrade to 4.1.30 or 5.0.27. > > Regards, > Steffen > > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > ___ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now. http://promotions.yahoo.com/goldrush - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: ThreadPool: Pool exhausted with 100 threads
Hi > Has anyone been able to solve or work around this problem under Tomcat 3.2.1? Any reasaon for this? There is hardly anyone who can help you with 3.x. 3.x is of stone age, 4.0.x is already very old, 4.1.x is maintained but also not current, and 5.0 is already stable for a while. Even 5.5 is available but in early stages. If possible, try to upgrade to 4.1.30 or 5.0.27. Regards, Steffen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ThreadPool: Pool exhausted with 100 threads
Hi, Has anyone been able to solve or work around this problem under Tomcat 3.2.1? or does Tomcat 4.x eliminate the pool exhausted problem? We are running a medium load ASP and run into this problem on 1 out of 4 servers each day, even though we restart Tomcat nightly in effort to avoid it. Ideally we wouldn't have to restart Tomcat more than once every 2-3 weeks. Any help much appreciated, Matt > At 12:56 PM 9/5/2001, you wrote: > >Hello, > > > >We are seeing many many 'ThreadPool: Pool exhausted > with 100 threads' > >errors. Ive seen that you can modify the > server.xml > to customize threadpool > >access (max_threads value=x max_spare_threads > vaule=x, min_spare_threads > >value=x), but Ive also heard that its hard coded in > >org.apache.tomcat.util.ThreadPool.java in Tomcat > 3.2.2. This is our > >production env so Id hate to impliment this and > have > the prolem become > >bigger. What do you guys suggest? We are using > Tomcat 3.2.2, Apache 1.3 > >(with ssl mod) as our webservers, on Solaris 7, > with > Oracle 8 via jdbc. > > You could up the values and re-compile. > > > > > > ___ > Do you Yahoo!? > Win 1 of 4,000 free domain names from Yahoo! Enter > now. > http://promotions.yahoo.com/goldrush > __ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Error: ThreadPool: Pool exhausted with 100 threads.
I've gotten a similar problem with Tomcat 4.0.4. Somehow I am able to tie up all available processors (as if they were blocked and can't wake up). I've even tried interrupting the threads repeatedly to try and "free" them up again, but that doesn't seem to work. Anyone have experience or suggestions regarding this? -Original Message- From: Ben Litchfield [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 11, 2002 12:45 PM To: [EMAIL PROTECTED] Subject: Error: ThreadPool: Pool exhausted with 100 threads. [EmbeddedTomcatSX] 2002-09-11 14:55:12 - ThreadPool: Pool exhausted with 100 threads. I have gotten this message several times. I am running Jboss-2.4.1_Tomcat-3.2.3. The server become unresponsive at this point and needs to be restarted to fix it. Any suggestions. Ben Litchfield -- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Error: ThreadPool: Pool exhausted with 100 threads.
[EmbeddedTomcatSX] 2002-09-11 14:55:12 - ThreadPool: Pool exhausted with 100 threads. I have gotten this message several times. I am running Jboss-2.4.1_Tomcat-3.2.3. The server become unresponsive at this point and needs to be restarted to fix it. Any suggestions. Ben Litchfield -- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
ThreadPool: pool exhausted with 100 threads
hello, i'm running tomcat 3.2.3 on jboss 2.4.1a and after several days of heavy use i'm getting the following message from tomcat on the console: ThreadPool: pool exhausted with 100 threads i checked in the tomcat.properties file and it looks like the thread pool stuff is set to false. i searched the lists and noticed that other people have had this problem but didn't see a solution listed. did i miss something? does anyone know how to fix this? thanks! chris | chris wilson || web dev ||| [EMAIL PROTECTED] || | www.wondergeek.com | | -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
Re: ThreadPool: Pool exhausted with 100 threads
At 12:56 PM 9/5/2001, you wrote: >Hello, > >We are seeing many many 'ThreadPool: Pool exhausted with 100 threads' >errors. Ive seen that you can modify the server.xml to customize threadpool >access (max_threads value=x max_spare_threads vaule=x, min_spare_threads >value=x), but Ive also heard that its hard coded in >org.apache.tomcat.util.ThreadPool.java in Tomcat 3.2.2. This is our >production env so Id hate to impliment this and have the prolem become >bigger. What do you guys suggest? We are using Tomcat 3.2.2, Apache 1.3 >(with ssl mod) as our webservers, on Solaris 7, with Oracle 8 via jdbc. You could up the values and re-compile.
ThreadPool: Pool exhausted with 100 threads
Hello, We are seeing many many 'ThreadPool: Pool exhausted with 100 threads' errors. Ive seen that you can modify the server.xml to customize threadpool access (max_threads value=x max_spare_threads vaule=x, min_spare_threads value=x), but Ive also heard that its hard coded in org.apache.tomcat.util.ThreadPool.java in Tomcat 3.2.2. This is our production env so Id hate to impliment this and have the prolem become bigger. What do you guys suggest? We are using Tomcat 3.2.2, Apache 1.3 (with ssl mod) as our webservers, on Solaris 7, with Oracle 8 via jdbc. Mucho Thanks ::'::amy... end.transmission...::':: \\*//
ThreadPool: Pool exhausted with 100 threads.
Hi All I am getting the following message written at console and tomcat server is not responding once the message is displayed. Next few sentences are from the tomcat.properties file for the Thread pool # # Thread Pool parameters # # Enables or disables the use of the thread pool. # Syntax: pool=[true|false] (boolean) # Default: false # WARNING: the pool has not been extensively tested and may generate deadlocks. # For this reason, we advise against using this code in production environments. pool=false # Indicates the number of idle threads that the pool may contain. # Syntax: pool.capacity=(int)>0 # Default: 10 # NOTE: depending on your system load, this number should be low for contantly # loaded servers and should be increased depending on load bursts. pool.capacity=10 # Indicates the pool controller that should be used to control the # level of the recycled threads. # Syntax: pool.controller=[full class of controller] (String) # Default: org.apache.java.recycle.DefaultController # NOTE: it is safe to leave this unchanged unless special recycle behavior # is needed. Look at the "org.apache.java.recycle" package javadocs for more # info on other pool controllers and their behavior. pool.controller=org.apache.java.recycle.DefaultController Although the pool=false is mentioned its still giving the same message. Could anyone please help me in finding solution for this problem. I have searched in archives but did'nt found any reply to these sort of questions. 2. I would also like to increase the cache memory and heap memory while starting tomcat server. Please help me out. Thanks in advance Krishna __ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/
ThreadPool: Pool exhausted with 100 threads.
Hi All I am getting the following message written at console and tomcat server is not responding once the message is displayed. Next few sentences are from the tomcat.properties file for the Thread pool # # Thread Pool parameters # # Enables or disables the use of the thread pool. # Syntax: pool=[true|false] (boolean) # Default: false # WARNING: the pool has not been extensively tested and may generate deadlocks. # For this reason, we advise against using this code in production environments. pool=false # Indicates the number of idle threads that the pool may contain. # Syntax: pool.capacity=(int)>0 # Default: 10 # NOTE: depending on your system load, this number should be low for contantly # loaded servers and should be increased depending on load bursts. pool.capacity=10 # Indicates the pool controller that should be used to control the # level of the recycled threads. # Syntax: pool.controller=[full class of controller] (String) # Default: org.apache.java.recycle.DefaultController # NOTE: it is safe to leave this unchanged unless special recycle behavior # is needed. Look at the "org.apache.java.recycle" package javadocs for more # info on other pool controllers and their behavior. pool.controller=org.apache.java.recycle.DefaultController Although the pool=false is mentioned its still giving the same message. Could anyone please help me in finding solution for this problem. I have searched in archives but did'nt found any reply to these sort of questions. 2. I would also like to increase the cache memory and heap memory while starting tomcat server. Please help me out. Thanks in advance Krishna __ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/
Re: Help on: "ThreadPool: pool exhausted with 100 threads"
Ooh! Shai is getting similar error. Although in his case he runs out of memory. But both of your errors occur in their ThreadPool program. I wonder if threads are not being returned to the pool, in which case you would need to report it as a bug. Json, how many connectors did you configure for this context? - Original Message - From: "Jayson Yu" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 18, 2001 10:49 AM Subject: Help on: "ThreadPool: pool exhausted with 100 threads" > hi, I was wondering if anybody can provide me some leads on how to deal > with this > problem... I have a servlet that queries a database and churns out (in > response) a > data populated html, however after some time and several hits on the > servlet, I get > the Tomcat error that "ThreadPool: pool exhausted with 100 threads". > > I'm not so sure if this is a tomcat or servlet problem, would > certainly appreciate if anybody can provide some help. tia! > > json >
Help on: "ThreadPool: pool exhausted with 100 threads"
hi, I was wondering if anybody can provide me some leads on how to deal with this problem... I have a servlet that queries a database and churns out (in response) a data populated html, however after some time and several hits on the servlet, I get the Tomcat error that "ThreadPool: pool exhausted with 100 threads". I'm not so sure if this is a tomcat or servlet problem, would certainly appreciate if anybody can provide some help. tia! json
