On Mon, 2008-10-27 at 09:20 -0600, Filip Hanik - Dev Lists wrote: > -1 But it's a complex situation: - java.io maxThreads includes threads also doing keepalive, so it means the connector will perform very bad once maxThreads is reached; since it does not represent the number of threads actually doing something, it can be increased very liberally, it will only use some memory - APR maxThreads only includes threads somewhere in the applications, and the connector should continue running acceptably once this is reached; increasing maxThreads too much poses a risk of excessive locking in applications (access to pools, etc)
Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
