Just thought I should post that it looks like the problems I'm having have nothing to do with mod_jk, tomcat or apache. After diagnosing with Redhat, it looks like there is some sort of incompatibility between the NIC's on these new servers and the Redhat driver.
When we force the NIC into 100MB full duplex mode autonegotiation off, the connection problems go away. Unfortunately, since we are using an unmanaged Netgear switch, it defaults the port down to Half Duplex when the other side is not set to autonegotiation. So, we have a new problem, but at least it's more isolated. Thanks, -Michael --- michael thomas <[EMAIL PROTECTED]> wrote: > I apologize for all the messages. But I thought > this > might also be useful info: > > Normally, when I run: netstat -tn | egrep > "^tcp.*:8009" > on the web server and the app server, the > connections > match up. > > However, after I start getting the errors below, > they > seem to not. For example, I currently have the > following on the web server: > > [EMAIL PROTECTED] access]# netstat -tn | egrep > "^tcp.*:8009" > tcp 0 0 10.0.0.212:53768 > 10.0.0.9:8009 ESTABLISHED > tcp 0 0 10.0.0.212:53772 > 10.0.0.9:8009 ESTABLISHED > > [EMAIL PROTECTED] ~]$ netstat -tn | egrep "^tcp.*:8009" > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53772 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53768 ESTABLISHED > tcp 0 3084 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53181 ESTABLISHED > tcp 0 1660 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53180 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53182 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53177 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53176 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53179 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53178 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53173 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53174 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53169 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53168 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53170 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53165 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53167 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53166 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53161 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53163 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53157 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53156 ESTABLISHED > tcp 0 3108 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53158 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53152 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53155 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53154 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53149 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53148 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53151 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53150 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53145 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53146 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53141 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53143 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53129 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53184 ESTABLISHED > tcp 0 0 ::ffff:10.0.0.9:8009 > ::ffff:10.0.0.212:53187 ESTABLISHED > > Thanks, > -Michael > > > But I have the following on the app server: > > > --- michael thomas <[EMAIL PROTECTED]> wrote: > > > We actually are seeing error messages in the > mod_jk > > logs now: > > > > [Sun Feb 26 01:02:52 2006] [12249:43360] [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 > > > > [Sun Feb 26 01:02:52 2006] [12249:43360] [error] > > ajp_get_reply::jk_ajp_common.c (1503): Tomcat is > > down > > or refused connection. No response has been sent > to > > the client (yet) > > > > These are recoverable errors, so I'm not sure if > > they're responsible for the problems we're having, > > but > > they sure don't look good. > > > > We have no firewall between Apache and Tomcat. > > MaxRequestsPerChild is 0 > > And we haven't set the recycle_timeout or > > socket_timeout in workers.properties, so they > should > > be non-issues. > > > > Also, I have seen that in the last few months, > there > > have been quite a few threads on this, with no > real > > apparent solution. > > > > I'm wondering if the thread posters found a > > solution. > > > > We've also seen messages like this: > > > > [Sun Feb 26 01:04:16 2006] [12248:2400] [info] > > ajp_service::jk_ajp_common.c (1749): Sending > request > > to tomcat failed, recoverable operation attempt=1 > > [Sun Feb 26 01:04:16 2006] [12248:2400] [info] > > ajp_send_request::jk_ajp_common.c (1178): Socket > 19 > > is > > not connected any more (errno=-1) > > [Sun Feb 26 01:04:16 2006] [12248:2400] [info] > > ajp_send_request::jk_ajp_common.c (1202): Error > > sending request. Will try another pooled > connection > > [Sun Feb 26 01:04:16 2006] [12248:2400] [info] > > ajp_send_request::jk_ajp_common.c (1225): All > > endpoints are disconnected or dead > > [Sun Feb 26 01:04:16 2006] [12248:2400] [info] > > ajp_service::jk_ajp_common.c (1749): Sending > request > > to tomcat failed, recoverable operation attempt=2 > > [Sun Feb 26 01:04:16 2006] [12248:2400] [debug] > > jk_open_socket::jk_connect.c (328): socket > > TCP_NODELAY > > set to On > > [Sun Feb 26 01:04:16 2006] [12248:2400] [debug] > > jk_open_socket::jk_connect.c (426): trying to > > connect > > socket 7 to 10.0.0.9:8009 > > [Sun Feb 26 01:04:16 2006] [12248:2400] [info] > > jk_open_socket::jk_connect.c (444): connect to > > 10.0.0.9:8009 failed with errno=111 > > [Sun Feb 26 01:04:16 2006] [12248:2400] [info] > > ajp_connect_to_endpoint::jk_ajp_common.c (889): > > Failed > > opening socket to (10.0.0.9:8009) with (errno=111) > > [Sun Feb 26 01:04:16 2006] [12248:2400] [info] > > ajp_send_request::jk_ajp_common.c (1248): Error > > connecting to the Tomcat process. > > [Sun Feb 26 01:04:16 2006] [12248:2400] [info] > > ajp_service::jk_ajp_common.c (1749): Sending > request > > to tomcat failed, recoverable operation attempt=3 > > [Sun Feb 26 01:04:16 2006] [12248:2400] [error] > > ajp_service::jk_ajp_common.c (1758): Error > > connecting > > to tomcat. Tomcat is probably not started or is > > listening on the wrong port. worker=app01 failed > > [Sun Feb 26 01:04:16 2006] [12248:2400] [debug] > > ajp_done::jk_ajp_common.c (2074): recycling > > connection > > cache slot=2 for worker app01 > > [Sun Feb 26 01:04:16 2006] [12248:2400] app01 > > www.mysite.com 802.465676 POST /index.jsp > > > === message truncated === __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
