Hash: SHA1


On 4/13/2010 3:53 PM, Russell Uman wrote:
> tomcat server.xml:
>     <Connector port="8009"
>     enableLookups="false" redirectPort="8443" protocol="AJP/1.3"
>         minSpareThreads="5" maxThreads="300"
>         connectionTimeout="120000" URIEncoding="UTF-8" />
> apache 2.0.52/mod_jk 1.2.19 workers.properties
>         worker.default.port=8009
>         worker.default.type=ajp13
>         worker.default.connect_timeout=120000
>         worker.default.connection_pool_timeout=120
>         worker.default.prepost_timeout=120000
>         worker.default.reply_timeout=1800000
>         worker.default.retries=1
> apache 2.2.3/mod_proxy_ajp
>     ProxyPass / ajp://example.org:8009/ timeout=1800 keepalive=on

120 seconds is a long time to wait for an HTTP request to show up. Is
that really what you wanted? Also, 1800 seconds (aka 30 minutes) is a
long time for a response. Are you sure these are reasonable values for
your application?

You have set prepost_timeout, but haven't set a ping_mode. Are you
seeing pings being sent? 120 seconds is a long time to wait for an AJP
connection to be made (or to reply to a ping). Again, are these values sane?

Glad to see that mod_jk is working well for you. Pid is right: 2.2.3 was
a loooong time ago in terms of mod_proxy_ajp. It's unfortunate that
package managers (RedHat, CentOS, Debian, etc.) move relatively slowly
when it comes to incorporating features such as these. It's
understandable, as most admins want stability over everything else.

Using mod_jk will give you the best experience if you are stuck with a
package-managed version of httpd, but are free to install hand-rolled
modules such as mod_jk.

- -chris
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to