DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38227>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38227 ------- Additional Comments From [EMAIL PROTECTED] 2006-02-21 16:57 ------- I have experienced the same bug, the problem also seem to cause the tomcat server (5.0.28) to run out of threads, I assume the problem is also causing the ajp threads not to be closed, so I assume using a retry will not help. Yet to confirm whether using prefork instead of worker fixes the problem, but I'll try this and add this to the bug report. ajp_read_header: ajp_ilink_receive failed (120006)APR does not understand this error code: proxy: read response failed from (null) (<ip_addr_here>) Then later proxy: AJP: failed to make connection to backend: <ip_addr_here> (110)Connection timed out: proxy: AJP: attempt to connect to <ip_addr_here>:8009 (<ip_addr_here>) failed It looks like tomcat can recover if it is under light load and the threads timeout, but when the load increases tomcat dies as all the threads get used up -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
