> The system seems to work fine from a user's > perspective, but we still occasionally get these: > > [Wed Mar 01 20:00:42 2006] [error] > ajp_connection_tcp_get_message::jk_ajp_common.c (961): > Can't receive the response message from tomcat, > network problems or tomcat is down (10.0.0.9:8009), > err=-113 > [Wed Mar 01 20:00:42 2006] [error] > ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down > or refused connection. No response has been sent to > the client (yet) > [Wed Mar 01 20:00:42 2006] [info] > ajp_service::jk_ajp_common.c (1721): Receiving from > tomcat failed, recoverable operation attempt=0 > [Wed Mar 01 20:00:42 2006] [info] > ajp_service::jk_ajp_common.c (1749): Sending request > to tomcat failed, recoverable operation attempt=1 > > For what it's worth, we have other completely separate > system setups using mod_jk2, and they also all seem to > get occasional ajp errors. This is our first setup > using mod_jk, and we are assuming these errors are a > bad thing.
I always had those errors. I did anything i could do - change timeouts, change backlog, change this, change that - whatever - these errors remain. Just make sure, that the tomcat allows as much or more ajp-connctions, than there will be apache-processes/threads. I think the programmers have given up on solving this - whatever the problem is. AFAIK, mod_jk prints that error-messages to the log and then tries another connect which usually works. Actually i hear the developers say: "this is not a problem" - or something like that. Well, no comment on that ... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
