Hello, I'm writing because at last we are about to upgrade the Apache httpd+mod_jk we use in the production environment from version 2.0.52 to version 2.2.14 (on Linux Servers), and I'd like to receive advice from you about timeout settings.
For some reason I don't know, the system has the following *odd* configuration: * Apache Timeout directive is not used (I assume that it times out after the default 300 seconds) * mod_jk is configured with connection_pool_timeout=5 & socket_timeout=5 (and it also has connection_pool_size=1) * Tomcat has its AJP connector configured to timeout after 300000 milliseconds I believe that the mod_jk timeouts are a bit too low, especially if compared to the other ones. We are experiencing a strange behaviour with our current configuration, and I believe it may be related to the configuration settings: many Tomcat threads get stuck while flushing the output buffer (in particular when the system is under heavy load), as if there were no other thread on the Apache side to receive their input. Do you think it is reasonable to have timeout values that differ so much between mod_jk and Tomcat? I'd rather us a connection_pool_timeout that's comparable to the Apache timeout, especially because we need to get rid of anything that may cause our workers to behave in such a weird manner. Thank you for any help you can give. Regards, Alessandro PS this post is related to this thread: http://mail-archives.apache.org/mod_mbox/tomcat-users/200911.mbox/%3cce3aa0b60911180337o6469bdb4tcf3a90b44cea4...@mail.gmail.com%3 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
