> Whenever you have connection pool setup
> in mod_jk it means you don't have constant connections
> any more. The connection pool will maintain the
> connections and close them by some rule (size).
> Now, having that you *must* have connectionTimeout="60000"
> in server.xml for the AJP connector so Tomcat can close
> his part of the connection as well.
I see. I added the connectionTimeout="60000" as suggested, using now
<!-- Define an AJP 1.3 Connector on port 8009 -->
<Connector port="8009"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3"
connectionTimeout="60000"/>
in my server.xml, everything else is still the same. We then subjected our
webserver to 2 users who were rapidly clicking on web links within our site
for a few minutes, about twice as fast as the service could respond. Tomcat
now reports a Current thread count: 27 , and it coesn't come down after the
connection_pool_timeout=600 (10 minutes) to the expected
connection_pool_minsize=10 TCP connections (= number of remaining minimum
threads?). The maximum number of HTTP Sessions was 10 according to our
session listener. The web service still receives requests and responds
normally, yet mod_jk now always comes up with this in its mod_jk.log:
.....
[Tue Jan 23 17:56:42 2007] [0436:2428] [error] jk_ajp_common.c (948):
(ajp13) can't receive the response message from tomcat, network problems or
tomcat is down (127.0.0.1:8009), err=-53
[Tue Jan 23 17:56:42 2007] [0436:2428] [error] jk_ajp_common.c (1566):
(ajp13) Tomcat is down or refused connection. No response has been sent to
the client (yet)
[Tue Jan 23 17:56:42 2007] [0436:2428] [info] jk_ajp_common.c (1877):
(ajp13) receiving from tomcat failed, recoverable operation attempt=0
[Tue Jan 23 17:56:42 2007] [0436:2428] [info] jk_ajp_common.c (1916):
(ajp13) sending request to tomcat failed, recoverable operation attempt=1
[Tue Jan 23 17:56:42 2007] [0436:2428] [error] jk_ajp_common.c (948):
(ajp13) can't receive the response message from tomcat, network problems or
tomcat is down (127.0.0.1:8009), err=-53
[Tue Jan 23 17:56:42 2007] [0436:2428] [error] jk_ajp_common.c (1566):
(ajp13) Tomcat is down or refused connection. No response has been sent to
the client (yet)
[Tue Jan 23 17:56:42 2007] [0436:2428] [info] jk_ajp_common.c (1877):
(ajp13) receiving from tomcat failed, recoverable operation attempt=1
[Tue Jan 23 17:56:42 2007] [0436:2428] [info] jk_ajp_common.c (1916):
(ajp13) sending request to tomcat failed, recoverable operation attempt=2
[Tue Jan 23 17:56:42 2007] [0436:2428] [error] jk_ajp_common.c (1928):
(ajp13) Connecting to tomcat failed. Tomcat is probably not started or is
listening on the wrong port
[Tue Jan 23 17:56:42 2007] ajp13 daohprw2 0.296977 GET /ohpr/servlet/
HTTP/1.1 200
[Tue Jan 23 17:56:42 2007] [0436:2428] [info] mod_jk.c (2142): Service
error=0 for worker=ajp13
.....
So it looks like the connection pool doesn't recover for some unkown
reasons. Is there anything else I have missed out on? Not restarting the
Apache2 and Tomcat NT services clears up this stalemate scenario, only a
complete server reboot does it.
J.Neuhoff
--
View this message in context:
http://www.nabble.com/mod_jk-replacement--tf3050993.html#a8527029
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
