We have web application using: tomcat 3.3.2, appache 1.3.29, Ajp13, BAS4.5.1, Oracle. During working hours, when load was high, it happend that tomcat stopped service requests from apache. Number of threads of apache increased, number of tomcat's thread increased as well (looked like tomcat allocated threads for apache requests, but they were not processed - no application logs) In the same time, tomcat properly serviced http requests (no apache) and freely communicate with app server. Problem was solved by tomcat restart
Tomcat 3.3 is not being actively developed. While this might receive attention from the one or two committers still interested in it, this attention may also never arrive, or may not be timely enough for dealing with this production issue. We recommend you upgrade to Tomcat 5.5.9.
(In reply to comment #1) > Tomcat 3.3 is not being actively developed. While this might receive attention > from the one or two committers still interested in it, this attention may also > never arrive, or may not be timely enough for dealing with this production > issue. We recommend you upgrade to Tomcat 5.5.9. Yoav is talking out his a** as usual. I won't make any difference. Tomcat 3.3 and Tomcat 5.5.9 use the identical Connectors so any problem like this in 3.3 will occur in 5.5 as well. A thread-dump of the hung Tomcat would be extremly helpful. Otherwise with the information here it isn't even possible to rule out a long GC pause.
Bill, I won't sink down to your childish insulting level. Everything I said in my response is true. If the problem is not in the connector (as you noted, it's impossible to know from the info provided), then what I said is especially relevant. It's good advice in general to use the latest stable, most actively supported version of a product, and not just a sub-component of it.
Created attachment 15807 [details] tomcat.log Pleas, find in the attachment tomcat logs from time the problem occured
It seems that you are using the (deprecated) AJP12Interceptor with the AJP/1.3 version of mod_jk. Try again with the Coyote AJP/1.3 Connector (or even the AJP13Interceptor.