OK, my mail was slightly misleading: the other timeouts should *not* bea
a reason for error -54. The one that could be a source of trouble is
socket_timeout. You've got it in your configuration. Delete it and try,
if this fixes the problem - might be.
Tie messages to requests: No easy way. For Apache I would say, in the
mod_jk error log we log process ID and thread ID. You can log these too
in the apache access logs and then it's very likely, that only a few
lines will fit timestamp, and those two IDs. I don't know much about IIS
access logs.
Using mod_jk only, you would need to increase log level to debug. Then,
if you get your error, you pick out the lines before with the same PID
and TID and there will be log statements containing the URL.
To anylyze one would try to sniff and find out, if at the time of the
-54, there was a connection reset packat from the remote side, or if the
reset has been done solely by the local TCP/IP stack. in this case I
would suppose it's a socket timeout issue. In the other case (reset
packet) one would need to invest, what is the remote side (firewall?)
and to find out, why the remote side resets the connection.
There is a normal use case of closing the connection by the remote side,
the connectionTimeout of the tomcat connector. It's normal to use this
feature and mod_jk normally logs only an info message and opens a new
one. This feature should not produce the kind of situation you are
experiencing.
Regards,
Rainer
Per Johnsson wrote:
Hi!
Thanks for the answare!
As far as we know and according to the networking guys there has been no
changes in the firewall and the load balancer, but I must admit that it
is a very tempting error. The problem is that we have a hard time to
localize the problem, we even can't se that the firewall or the lb is
the problem and our environment is not so flexible that we just could
bypass it to test.
connection_pool_timeout - This one seems not to be an issue, if this
would be applicible then we would get some thread errors on the tomcat
side, but tomcat seems to run smooth as nothing had happend.
prepost_timeout - This one, as I see it is good if tomcat hangs but
that's not our problem.
reply_timeout - Could be interesting but as I understand it the default
value is 0 (infinite) even if not defined?
Is there a good way to see if the firewall or the lb is reseting our
connections? Some tools or special debug/log?
Is there a way to see in the connector logs the url's or something to
tie the error to an actual event?
This is our worker properties:
---8<---
worker.list=ajp13w,ajp15w
#
# Defining a worker named ajp13w and of type ajp13
# Note that the name and the type do not have to match.
#
worker.ajp13w.type=ajp13
worker.ajp13w.host=10.182.19.3
worker.ajp13w.port=8009
worker.ajp13w.socket_keepalive=True
worker.ajp13w.connection_pool_size=120
worker.ajp15w.type=ajp13
worker.ajp15w.host=10.182.18.2
worker.ajp15w.port=8009
worker.ajp15w.socket_keepalive=True
worker.ajp15w.socket_timeout=60
---8<---
/Per Jonsson
-----Original Message-----
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: den 23 februari 2007 09:25
To: Tomcat Users List
Subject: Re: Still connection problems between IIS tomcat 5.5.12....
Winsock error 10054 is a connection reset.
Do you use socket_timeout in workers.properties? If yes, try without
socket_timeout (but have a look at the other timeout possibilities of
mod_jk). Socket_timeout is difficult to handle at the application=mod_jk
layer.
Any changes on the firewall around the time your trouble began?
Regards,
Rainer
Per Johnsson wrote:
It's me again, we have not yet solved our problems, but now we have
turned one of the IIS servers to IIS 5 compability mode which made us
get som logs from the tomcat connector.
Short Review of setup:
Tomcat 5.5.12
APR 1.1.0-dev
ispi_redirect.dll 1.2.20
between the iis and tomcat we have a firewall and a load balancer and
it have worked very good in about a year until 1/2-2007 where the IIS
started to crash without any hardware and software changes (what we
know
of)
The thing is that Tomcat seems to run fine, we can't se any problems
on the tomcat side so I wonder if anyone have any suggestions.
(We have looked at the firewall and load balancer and there should not
be any problems there, otherwise that seemed to be a good error
source.)
My intepretation is that the connector can send the request but don't
get any response, could that be correct?
Any input is more than welcome!
Here is a snip from our connector log:
---8<---
[Wed Feb 21 23:11:32 2007] [4580:7020] [error] jk_ajp_common.c (948):
(ajp13w) can't receive the response message from tomcat, network
problems or tomcat is down (10.182.19.2:8009), err=-54 [Wed Feb 21
23:11:32 2007] [4580:7020] [error] jk_ajp_common.c (1566):
(ajp13w) Tomcat is down or refused connection. No response has been
sent to the client (yet) [Wed Feb 21 23:11:32 2007] [4580:7020]
[error] jk_ajp_common.c (948):
(ajp13w) can't receive the response message from tomcat, network
problems or tomcat is down (10.182.19.2:8009), err=-54 [Wed Feb 21
23:11:32 2007] [4580:7020] [error] jk_ajp_common.c (1566):
(ajp13w) Tomcat is down or refused connection. No response has been
sent to the client (yet) [Wed Feb 21 23:11:32 2007] [4580:7020]
[error] jk_ajp_common.c (1928):
(ajp13w) Connecting to tomcat failed. Tomcat is probably not started
or is listening on the wrong port [Wed Feb 21 23:11:32 2007]
[4580:7020] [error] jk_isapi_plugin.c (1098):
service() failed
[Thu Feb 22 02:36:13 2007] [4580:4524] [error] jk_ajp_common.c (948):
(ajp15w) can't receive the response message from tomcat, network
problems or tomcat is down (10.182.18.2:8009), err=-54 [Thu Feb 22
02:36:13 2007] [4580:4524] [error] jk_ajp_common.c (1566):
(ajp15w) Tomcat is down or refused connection. No response has been
sent to the client (yet) [Thu Feb 22 02:36:13 2007] [4580:4524]
[error] jk_ajp_common.c (948):
(ajp15w) can't receive the response message from tomcat, network
problems or tomcat is down (10.182.18.2:8009), err=-54 [Thu Feb 22
02:36:13 2007] [4580:4524] [error] jk_ajp_common.c (1566):
(ajp15w) Tomcat is down or refused connection. No response has been
sent to the client (yet) [Thu Feb 22 02:36:13 2007] [4580:4524]
[error] jk_ajp_common.c (1928):
(ajp15w) Connecting to tomcat failed. Tomcat is probably not started
or is listening on the wrong port [Thu Feb 22 02:36:13 2007]
[4580:4524] [error] jk_isapi_plugin.c (1098):
service() failed
[Thu Feb 22 03:56:51 2007] [4580:7940] [error] jk_ajp_common.c (948):
(ajp13w) can't receive the response message from tomcat, network
problems or tomcat is down (10.182.19.2:8009), err=-54 [Thu Feb 22
03:56:51 2007] [4580:7940] [error] jk_ajp_common.c (1566):
(ajp13w) Tomcat is down or refused connection. No response has been
sent to the client (yet) [Thu Feb 22 03:56:51 2007] [4580:7940]
[error] jk_ajp_common.c (948):
(ajp13w) can't receive the response message from tomcat, network
problems or tomcat is down (10.182.19.2:8009), err=-54 [Thu Feb 22
03:56:51 2007] [4580:7940] [error] jk_ajp_common.c (1566):
(ajp13w) Tomcat is down or refused connection. No response has been
sent to the client (yet) [Thu Feb 22 03:56:51 2007] [4580:7940]
[error] jk_ajp_common.c (1928):
(ajp13w) Connecting to tomcat failed. Tomcat is probably not started
or is listening on the wrong port [Thu Feb 22 03:56:51 2007]
[4580:7940] [error] jk_isapi_plugin.c (1098):
service() failed
[Thu Feb 22 07:40:25 2007] [4580:4244] [error] jk_ajp_common.c (948):
(ajp13w) can't receive the response message from tomcat, network
problems or tomcat is down (10.182.19.2:8009), err=-54 [Thu Feb 22
07:40:25 2007] [4580:4244] [error] jk_ajp_common.c (1566):
(ajp13w) Tomcat is down or refused connection. No response has been
sent to the client (yet) [Thu Feb 22 07:43:41 2007] [4580:7940]
[error] jk_ajp_common.c (948):
(ajp15w) can't receive the response message from tomcat, network
problems or tomcat is down (10.182.18.2:8009), err=-54 [Thu Feb 22
07:43:41 2007] [4580:7940] [error] jk_ajp_common.c (1566):
(ajp15w) Tomcat is down or refused connection. No response has been
sent to the client (yet) [Thu Feb 22 08:40:08 2007] [4580:6404]
[error] jk_isapi_plugin.c (659):
WriteClient failed with 00002746
[Thu Feb 22 10:29:52 2007] [4580:5972] [error] jk_ajp_common.c (948):
(ajp13w) can't receive the response message from tomcat, network
problems or tomcat is down (10.182.19.2:8009), err=-54 [Thu Feb 22
10:29:52 2007] [4580:5972] [error] jk_ajp_common.c (1566):
(ajp13w) Tomcat is down or refused connection. No response has been
sent to the client (yet) [Thu Feb 22 10:32:34 2007] [4580:4608]
[error] jk_ajp_common.c (948):
(ajp15w) can't receive the response message from tomcat, network
problems or tomcat is down (10.182.18.2:8009), err=-54 [Thu Feb 22
10:32:34 2007] [4580:4608] [error] jk_ajp_common.c (1566):
(ajp15w) Tomcat is down or refused connection. No response has been
sent to the client (yet)
---8<---
Regards Per Jonsson
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
