You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2008/01/11 12:21:50 UTC
DO NOT REPLY [Bug 44207] - Apache 2.2.4+jk_ajp+Tomcat 5.5.17 Connect Error!
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=44207>.
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