Hi,
I am having a problem where tomcat keeps intermitantly starting new
ajp13 processor threads, eventually it reaches the max and starts
refusing connections. My hosting provider (linux machine) provides a
private version of tomcat for each user with a single apache web server,
there are typic
Hi,
I thought I would take a different tack on my problem with the
Ajp13Processor using up all of its threads problem.
Does anyone know if the Ajp13Processor has a timeout when it is looking
for a worker to handle a request? If the worker threads were all swapped
out and taking a long time to ge
One way to start debugging this type of problem is to tell the java
process running Tomcat to do a Thread Stacktrace Dump.
kill -QUIT
Then analyze the stack traces for all threads.
Regards,
Glenn
Lindsay Patten wrote:
Hi,
I thought I would take a different tack on my problem with the
Ajp13
Once an Apache process opens a socket connection to Tomcat for Ajp that
connection remains open until that httpd process dies. That way the
httpd process can reuse that connection. For Apache 1.3 there is a
one to one mapping between apache httpd processes and Tomcat Ajp13Processors.
You can end
Thanks again Glenn!
Now I've got something concrete to take to my service provider for
resolution.
Cheers,
Lindsay
Glenn Nielsen wrote:
Once an Apache process opens a socket connection to Tomcat for Ajp that
connection remains open until that httpd process dies. That way the
httpd process
Thanks for the pointer Glenn, it was much appreciated!
So, I've been doing thread stacktrace dumps, but what I found doesn't
make a lot of sense to me.
After restarting tomcat there were 5 processor threads all blocked on a
monitor:
"Ajp13Processor[8085][0]" daemon prio=1 tid=0x0x4f801b28 nid=0
