Could you switch to mod_jk found on jakarta-tomcat-connectors ?
It contains up to date codes and have timestamp in logs.
Write failed seems to indicate you have restarted Tomcat at some
time or may be you add too many mod_jk process in Apache compared
to available threads handling ajp13 in Tomcat.
-
Henri Gomez ___[_]____
EMAIL : [EMAIL PROTECTED] (. .)
PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
>-----Original Message-----
>From: Fran Fabrizio [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, July 11, 2001 5:51 PM
>To: [EMAIL PROTECTED]
>Subject: mod_jk.log messages
>
>
>
>I asked this last week and did not receive a reply, but I am unable to
>find documentation on these errors. Can anyone help?
>
>[jk_ajp13_worker.c (325)]: Error ajp13_process_callback - write failed
>[jk_ajp13_worker.c (325)]: Error ajp13_process_callback - write failed
>[jk_ajp13_worker.c (325)]: Error ajp13_process_callback - write failed
>[jk_ajp13_worker.c (325)]: Error ajp13_process_callback - write failed
>[jk_ajp13_worker.c (325)]: Error ajp13_process_callback - write failed
>[jk_ajp13_worker.c (325)]: Error ajp13_process_callback - write failed
>[jk_ajp13_worker.c (325)]: Error ajp13_process_callback - write failed
>
>without timestamps in this log, I can't really tell you how often it
>happens, but we're noticing slowdowns and weird behavior on our sites
>and we're wondering if this is the culprit. What causes this message
>and what does it mean?
>
>Thank you very much.
>
>Thanks,
>Fran
>
