I assume you put an Apache in front of your AJP connector? Then you need
to disable HTTP Keep-Alive in the Apache configuration. AJP 13 will
always use persistent connections between Apache and Tomcat.
The workers.properties attribute socket_keepalive has no relation to
HTTP Keep-Alive. The option configure TCP-Keepalive, which is sometimes
needed when Apache and Tomcat are connected via a firewall which drops
idle connections.
randy repasa wrote:
Hi Ian,
The config option you're looking for is not in the server.xml file, there's
a config option in workers.properties file that's specifically for
keepalive: socket_keepalive
If you want to disable keepalive for your app, you have to set this option
to zero:
worker.<worker name>.socket_keepalive=0
Hope this helps.
Randy
On 5/24/06, Ian Hunter <[EMAIL PROTECTED]> wrote:
I have an application that queries Tomcat quite frequently (more than
once
a minute) for status updates. I also have a potentially high number of
clients -- more that the number of threads configured for connectors.
Also, I'm using port 8009 for an AJP connector from Apache.
OK, that's all fine, here's my problem: the clients are all requesting
keepalives, and if there are more clients than threads, that's very bad.
I need to totally disable keepalives, but I cannot figure out how to
disable keepalives for the AJP connector. There's nothing in server.xml,
and I've tried KeepAlive Off in httpd.conf s well as
Jkworker.property.appname.KeepAlive Off.
Help?!?!
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
