DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25841>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25841 Tomcat/JK thread starvation [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2004-01-05 20:16 ------- There is a 1 <-> mapping between apache httpd processes and tomcat Processors. Once an httpd process has had to forward a request to Tomcat the connection it establishes to Tomcat is maintained until that httpd process dies, even if that httpd process never has to forward another request to Tomcat. So if apache is serving alot of normal http request which don't require Tomcat you end up with a large number of idle connections to Tomcat which use Processors. If you are running on unix and can use Apache 2 with the threaded worker MPM I recommend upgrading to that. This configuration makes much more efficient use of the connections between Tomcat and apache because multiple request handling threads in apache can share the same pool of connections to Tomcat. The stack trace you show just indicates that most of your AJP Processors are idle. This is not a bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
