On 28.06.2010 22:06, Rumpa Giri wrote:

We are trying to upgrade to the latest connector. While going through the
worker properties variables to set we have few questions regarding the
following -

Please do also grab the source tarball. In version 1.2.30 it contains an example configuration file that has a lot of helpful comments in it.

1) connection_pool_size -



Usually this is the same as the number of threads per web server process.
(cut-paste from the description for connection_pool_size)



I am not familiar with IIS - so how do you determine the above?

There was some debate, whether there's a way to automatically determine that. Microsoft doesn't really document it and it seems to depend a lot on IIS version and windows details. See also André's comments.

Also does this property have any correlation with the attribute MaxThreads
in the<Connector>  tag of server.xml? How do you determine what value should
you put for MaxThreads?

If there is only one Tomcat you are forwarding to, then it would be the same number. Tomcat - without the tcnative/APR connector - uses one thread per incoming connection.

Things get more complicated, if you start using IIS with multiple processes, or a farm of several Tomcats.

2) connection_pool_timeout - The server.xml - the default value if not
specified explicitly is 60000(60 secs). I see in our server.xml AJP
connector tag - its not specified - which means I do need to specify this
property connection_pool_timeout in our worker.properties as 60? The
documentation says the default for connection_pool_timeout is 0, shouldn't
it be 60 if this has to be in synch with server.xml?

It should be in sync (apart form the fact that one is in seconds and the other in milliseconds) and you should expliciteley set both. See the commented example config in the 1.2.30 source download.

3) The worker.loadbalancer.method property - currently not set - but we are
thinking of doing as B instead of default R. What do you use in general? Is
there a disadvantage to switching from Request to Busyness?

https://issues.apache.org/bugzilla/show_bug.cgi?id=44454

R should be good enough in most cases, except things like many parallel and long running requests, e.g. download farms for huge content.

Regards,

Rainer

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

Reply via email to