I'm having the same issue as documented in:
http://www.nabble.com/httpd-JK-Tomcat-hung-connections-td10403182.html
For our situation, we haven't hit the server reached MaxClients setting
issue yet, but we easily could.
We also have this same config running on a Windows cluster
On 10.10.2009 16:45, darinpope wrote:
I'm having the same issue as documented in:
http://www.nabble.com/httpd-JK-Tomcat-hung-connections-td10403182.html
For our situation, we haven't hit the server reached MaxClients setting
issue yet, but we easily could.
Use thread dumps to see, what
Please update mod_jk. 1.2.6 is *very* outdated. We are now at 1.2.22 and
a lot of things have improved.
After upgrading, check your configuration against the reference guide in
the docs, especially the pages for the worker properties and Apache
directives. You might want to add some more
Rainer,
Thanks for the reply! You're certainly right on the JK version.
Can you be more specific on the add some more timeouts comment? Do
you mean a higher number on connection_pool_timeout?
Also, should the relationship between httpd's MaxClients and the
connector's maxThreads be 1:1 or
Brantley Hobbs wrote:
Rainer,
Thanks for the reply! You're certainly right on the JK version.
Can you be more specific on the add some more timeouts comment? Do
you mean a higher number on connection_pool_timeout?
Have a look at connect_timeout and prepost_timeout. Usually I also use
Rainer,
Thanks for all the info. Hopefully we can get this thing whipped into
shape.
Brantley
Rainer Jung wrote:
Brantley Hobbs wrote:
Rainer,
Thanks for the reply! You're certainly right on the JK version.
Can you be more specific on the add some more timeouts comment? Do
you mean a