Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 51216 invoked from network); 11 Jan 2008 11:22:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Jan 2008 11:22:19 -0000 Received: (qmail 63045 invoked by uid 500); 11 Jan 2008 11:22:01 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 62997 invoked by uid 500); 11 Jan 2008 11:22:01 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 62986 invoked by uid 500); 11 Jan 2008 11:22:01 -0000 Delivered-To: apmail-jakarta-tomcat-dev@jakarta.apache.org Received: (qmail 62983 invoked by uid 99); 11 Jan 2008 11:22:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2008 03:22:01 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2008 11:21:45 +0000 Received: by brutus.apache.org (Postfix, from userid 33) id 27A2C714236; Fri, 11 Jan 2008 03:21:50 -0800 (PST) From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 44207] - Apache 2.2.4+jk_ajp+Tomcat 5.5.17 Connect Error! In-Reply-To: X-Bugzilla-Reason: AssignedTo Message-Id: <20080111112151.27A2C714236@brutus.apache.org> Date: Fri, 11 Jan 2008 03:21:50 -0800 (PST) X-Virus-Checked: Checked by ClamAV on apache.org DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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=44207 rainer.jung@kippdata.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From rainer.jung@kippdata.de 2008-01-11 03:21 ------- This is not an error. The log level of all messages is "info". The messages tell us, that when writing back to the client (=browser), mod_jk detected that it actually couldn't write back. Usually this simply means, that the browser didn't wait long enough for the response, but the user instead started another response (clicked another link, or the same link a second time etc.). If this happens a lot, it mostly is an indication, that your application performance is not good, so users get nervous and try something else. To get an idea about your appps response times, add "%D" to your httpd LogFormat (microseconds response duration) and maybe also add an access log valve to Tomcat with a pattern, that includes also "%D" (milliseconds for tomcat). If you have further questions, please ask the users list. -- 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: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org