Mladen, thanks for the response. I've been digging into the problem
with netstat a bit. Here is a log of the date, # of connections to
tomcat1, number of connections to tomcat2 (by netstat -a | grep
webserverIP | wc -l). At 10:58 I had to restart the apache because it
was in the "Stuck" state. It seems that the number of connections
between the apache and the tomcats just start escalating for some
reason. mod_jk.log shows a ton (>50) of these errors:
mod_jk.log
==========
[Wed Apr 05 10:57:35 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
(192.168.1.254:8089), err=-104
Wed Apr 05 10:57:35 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 Apr 05 10:57:35 2006] [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=tc1-w1 failed
[Wed Apr 05 10:57:35 2006] [info] service::jk_lb_worker.c (696):
service failed, worker tc1-w1 is in error state
It seems like some socket is not getting closed or something, and
resources are building up? BTW- jkstatus shows that my MaxBusy threads
as 10 and 8 respectively. Any ideas why it would be creating so many
sockets between apache and tomcat? Also- I was able to connect to
tomcat1 via its web port while things were wedged. Also- before a
previous crash/wedge, I noticed that the number of connections to tc1
was was dropping down to 10 or 12. Very confusing.
Thanks again for any insight...
/kurt
04/05/2006 10:52:35 AM 73 72
04/05/2006 10:52:45 AM 74 74
04/05/2006 10:52:56 AM 72 74
04/05/2006 10:53:06 AM 65 72
04/05/2006 10:53:17 AM 63 71
04/05/2006 10:53:27 AM 61 72
04/05/2006 10:53:37 AM 61 69
04/05/2006 10:53:48 AM 63 69
04/05/2006 10:53:58 AM 62 69
04/05/2006 10:54:09 AM 64 70
04/05/2006 10:54:19 AM 67 67
04/05/2006 10:54:30 AM 69 67
04/05/2006 10:54:41 AM 70 68
04/05/2006 10:54:52 AM 71 71
04/05/2006 10:55:02 AM 74 69
04/05/2006 10:55:12 AM 77 68
04/05/2006 10:55:23 AM 77 67
04/05/2006 10:55:33 AM 86 65
04/05/2006 10:55:44 AM 97 67
04/05/2006 10:55:54 AM 98 69
04/05/2006 10:56:04 AM 99 75
04/05/2006 10:56:15 AM 104 78
04/05/2006 10:56:25 AM 109 83
04/05/2006 10:56:36 AM 116 85
04/05/2006 10:56:46 AM 120 86
04/05/2006 10:56:56 AM 121 86
04/05/2006 10:57:07 AM 125 84
04/05/2006 10:57:17 AM 128 82
04/05/2006 10:57:28 AM 134 84
04/05/2006 10:57:39 AM 130 142
04/05/2006 10:57:49 AM 130 145
04/05/2006 10:58:00 AM 130 147
04/05/2006 10:58:11 AM 130 144
04/05/2006 10:58:21 AM 130 140
04/05/2006 10:58:32 AM 11 136
04/05/2006 10:58:43 AM 10 30
Mladen Turk wrote:
Kurt Overberg wrote:
[Tue Apr 04 18:23:35 2006] [info]
ajp_process_callback::jk_ajp_common.c (1384): Connection aborted or
network problems
[Tue Apr 04 18:23:35 2006] [info] ajp_service::jk_ajp_common.c
(1731): Receiving from tomcat failed, because of client error without
recovery in send loop 0
[Tue Apr 04 18:23:35 2006] [info] service::jk_lb_worker.c (711):
unrecoverable error 400, request failed. Client failed in the middle
of request, we can't recover to another instance.
[Tue Apr 04 18:23:35 2006] [info] jk_handler::mod_jk.c (1841):
Aborting connection for worker=loadbalancer
This means exactly what it says. The client has closed it's part
of connection in the middle of the request, thus Tomcat is responding
with 400 (Bad Request).
If you wish to get rid of those messaged rise the JkLogLevel to error.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
