Thank you David and Wade for this information.
I now have an idea what caused it. I have a fairly new programme that
uses too many threads, and I can deal with it.
However I would like to try the thread dump, but running kill -3 xxx
or kill -QUIT xxx on the first Tomcat thread found after
P.S. I've found the stack trace in catalina.out.
I thought I could pipe it to a file, but never mind.
Anyway thankyou for your help, I think I can get to the bottom of it all
now.
Wade Chandler wrote:
--- David Wall [EMAIL PROTECTED] wrote:
1) We have only a moderately busy site with
I've got Tomcat 4.1.30 and Apache 1.3 on Linux and I've been using the
jk2 connector for a year and a half without any problems.
Now I've suddenly got Tomcat stopping with the following message:
All threads (75) are currently busy, waiting. Increase maxThreads (75)
or check the servlet status.
1) We have only a moderately busy site with about 500 new visitors
entering from outside every day, so it would have thought it would be
fairly difficult for them to use up all the 75 connections at the same
time, but I do have some programmes that create their own threads,
though in a
--- David Wall [EMAIL PROTECTED] wrote:
1) We have only a moderately busy site with about
500 new visitors
entering from outside every day, so it would have
thought it would be
fairly difficult for them to use up all the 75
connections at the same
time, but I do have some