Caldarale, Charles R wrote:
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Subject: Re: Performance tricks with multiple tomcat instances
the select (non blocking) capability would be required
if you wanna do keep alive connections with less threads
than connections
that is why BEA early on did what Tomcat is doing with APR
right now, although tomcat is still doing blocking IO.
I'm not quite following; are you saying the APR connector does not use
one thread per connection, and the pure Java one does in a keepalive
environment? Does setting maxKeepAliveRequests to 1 for the HTTP
connector avoid keeping the non-busy threads around?
Tomcat APR will use one thread per connection. but APR also has non
blocking option.
maxKeepAliveRequests=1 --> keep alive false, and it will close the
connection. It might still keep the thread alive depending on your
maxSpareThreads setting.
Filip
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
