[Fri Jan 11 13:44:11 2008] [0348:4492] [info] jk_ajp_common.c (1448): Writing to client aborted or client network problems [Fri Jan 11 13:44:11 2008] [0348:4492] [info] jk_ajp_common.c (1857): (work3) request failed, because of client write error without recovery in send loop attempt=0 [Fri Jan 11 13:44:11 2008] [0348:4492] [info] mod_jk.c (2247): Aborting connection for worker=work3 [Fri Jan 11 13:44:12 2008] [0348:3856] [info] jk_ajp_common.c (1448): Writing to client aborted or client network problems [Fri Jan 11 13:44:12 2008] [0348:3856] [info] jk_ajp_common.c (1857): (work4) request failed, because of client write error without recovery in send loop attempt=0 [Fri Jan 11 13:44:12 2008] [0348:3856] [info] mod_jk.c (2247): Aborting connection for worker=work4 [Fri Jan 11 13:44:13 2008] [0348:3812] [info] jk_ajp_common.c (1448): Writing to client aborted or client network problems [Fri Jan 11 13:44:13 2008] [0348:3812] [info] jk_ajp_common.c (1857): (work3) request failed, because of client write error without recovery in send loop attempt=0 [Fri Jan 11 13:44:13 2008] [0348:3812] [info] mod_jk.c (2247): Aborting connection for worker=work3 [Fri Jan 11 13:44:14 2008] [0348:4492] [info] jk_ajp_common.c (1448): Writing to client aborted or client network problems [Fri Jan 11 13:44:14 2008] [0348:4492] [info] jk_ajp_common.c (1857): (work3) request failed, because of client write error without recovery in send loop attempt=0 [Fri Jan 11 13:44:14 2008] [0348:4492] [info] mod_jk.c (2247): Aborting connection for worker=work3
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.