Hi.
I impolitely invaded/hijacked another thread before, was (justifiably)
ignored as a result, and stand duly chastised.
I apologise and this is a new posting to the same effect.
I have a case very similar to one previously mentioned, at a customer,
running under RHEL 5, with Apache 2.0.x, mod_jk 1.2.28-dev and Tomcat
5.5.x.
(The mod_jk 1.2.6 originally installed showed the same issues, only
slightly different error messages; the mod_jk-dev version installed now
is one that was provided tome to correct another Apache segfault issue,
and I installed because of the ping-pong addition in the meantime).
Note that I am not saying that mod_jk has any responsibility in the
issue. It is just that the mod_jk log seems to be the only one that
actually shows where the error happens.
I see mod_jk messages as listed below (from mod_jk to client, and from
mod_jk to Tomcat). What concerns me is the ones to the clients.
These messages happen very regularly (every few minutes), sometimes in
bursts.
The browser is IE6, and often returns a "This page cannot be displayed"
("friendly IE error message", which unfortunately cannot be turned off
by the users, settings locked).
It is pretty-well established that the users do not click away from the
page and do not click the "cancel" button.
When users, after the IE error page, click the "reload" button, the same
request/response usually works fine.
The users are getting pretty p.. off by what they perceive as an
application problem, but we do not see a problem at the application
level (logfiles etc..).
The users say that this problem affects only this application and/or
server, but we do not know if they actually use any other comparable
service.
The server is hosted by a service company, in a location physically
distant from the users, but supposedly with good connectivity.
The server/application can sometimes take a while to respond to a
request, but never more than say 10 seconds at most, and the users kind
of know when they ask a heavy question, so they would not really get so
impatient.
The users are spread out, so even when monitoring the mod_jk log in real
time it is not easy to immediately connect one of these client-side
mod_jk error messages with the occurrence of an error at IE level. We
just kind of suppose that they are linked.
The problem is specific to that customer site. We have similar setups at
many other places, none of them exhibiting the same issue.
Any ideas/suggestions of what we could do to better pin-point the
problem ? (or of some setting to overcome it ?)
Thanks.
mod_jk log excerpt :
[Mon Jan 19 15:02:52 2009] [6802:4416] [info]
ajp_process_callback::jk_ajp_common.c (1447): Writing to client aborted
or client network problems
[Mon Jan 19 15:02:52 2009] [6802:4416] [info]
ajp_service::jk_ajp_common.c (1846): (ajp13) request failed, because of
client write error without recovery in send loop attempt=0
[Mon Jan 19 15:02:52 2009] [6802:4416] [info] jk_handler::mod_jk.c
(2190): Aborting connection for worker=ajp13
[Mon Jan 19 15:03:12 2009] [6804:4416] [info]
ajp_process_callback::jk_ajp_common.c (1447): Writing to client aborted
or client network problems
[Mon Jan 19 15:03:12 2009] [6804:4416] [info]
ajp_service::jk_ajp_common.c (1846): (ajp13) request failed, because of
client write error without recovery in send loop attempt=0
[Mon Jan 19 15:03:12 2009] [6804:4416] [info] jk_handler::mod_jk.c
(2190): Aborting connection for worker=ajp13
[Mon Jan 19 15:21:18 2009] [6952:4416] [info]
ajp_send_request::jk_ajp_common.c (1215): (ajp13) error sending request.
Will try another pooled connection
[Mon Jan 19 15:21:18 2009] [6952:4416] [info]
ajp_send_request::jk_ajp_common.c (1241): (ajp13) all endpoints are
disconnected
[Mon Jan 19 15:21:18 2009] [6952:4416] [info]
ajp_send_request::jk_ajp_common.c (1244): (ajp13) increase the backend
idle connection timeout or the connection_pool_minsize
[Mon Jan 19 15:21:18 2009] [6952:4416] [info]
ajp_service::jk_ajp_common.c (1930): (ajp13) sending request to tomcat
failed, recoverable operation attempt=1
[Mon Jan 19 15:27:04 2009] [7709:4416] [info]
ajp_process_callback::jk_ajp_common.c (1447): Writing to client aborted
or client network problems
[Mon Jan 19 15:27:04 2009] [7709:4416] [info]
ajp_service::jk_ajp_common.c (1846): (ajp13) request failed, because of
client write error without recovery in send loop attempt=0
[Mon Jan 19 15:27:04 2009] [7709:4416] [info] jk_handler::mod_jk.c
(2190): Aborting connection for worker=ajp13
[Mon Jan 19 15:27:50 2009] [7711:4416] [info]
ajp_send_request::jk_ajp_common.c (1215): (ajp13) error sending request.
Will try another pooled connection
[Mon Jan 19 15:27:50 2009] [7711:4416] [info]
ajp_send_request::jk_ajp_common.c (1241): (ajp13) all endpoints are
disconnected
[Mon Jan 19 15:27:50 2009] [7711:4416] [info]
ajp_send_request::jk_ajp_common.c (1244): (ajp13) increase the backend
idle connection timeout or the connection_pool_minsize
[Mon Jan 19 15:27:50 2009] [7711:4416] [info]
ajp_service::jk_ajp_common.c (1930): (ajp13) sending request to tomcat
failed, recoverable operation attempt=1
[Mon Jan 19 15:35:56 2009] [8076:4416] [info]
ajp_process_callback::jk_ajp_common.c (1447): Writing to client aborted
or client network problems
[Mon Jan 19 15:35:56 2009] [8076:4416] [info]
ajp_service::jk_ajp_common.c (1846): (ajp13) request failed, because of
client write error without recovery in send loop attempt=0
[Mon Jan 19 15:35:56 2009] [8076:4416] [info] jk_handler::mod_jk.c
(2190): Aborting connection for worker=ajp13
[Mon Jan 19 15:36:11 2009] [8075:4416] [info]
ajp_process_callback::jk_ajp_common.c (1447): Writing to client aborted
or client network problems
[Mon Jan 19 15:36:11 2009] [8075:4416] [info]
ajp_service::jk_ajp_common.c (1846): (ajp13) request failed, because of
client write error without recovery in send loop attempt=0
[Mon Jan 19 15:36:11 2009] [8075:4416] [info] jk_handler::mod_jk.c
(2190): Aborting connection for worker=ajp13
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
