We are using tomcat connector as follows --
Connector connectionTimeout=50 port=8080 protocol=HTTP/1.1 ...
Based on the documentation we are using the blocking call, right? So the
servlet thread is blocked for IO while reading request and writing response.
In case we want to use NIO, we
On 22/12/2010 16:31, shrikant patel wrote:
We are using tomcat connector as follows --
Connector connectionTimeout=50 port=8080 protocol=HTTP/1.1 ...
Based on the documentation we are using the blocking call, right?
It depends. Probably the BIO connector but it could also bee the APR
hi shrikant,
there are many benefits of NIO in a tomcat 6, the main being there is no longer
a thread-per-connection limit.
Note in Tomcat 7, even with the blocking connector, you can have more
connections than threads.
The NIO connector will read your request headers in a non blocking fashion,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shri,
On 12/22/2010 11:31 AM, shrikant patel wrote:
We are using tomcat connector as follows --
Connector connectionTimeout=50 port=8080 protocol=HTTP/1.1 ...
Aside from the comments made by others, I highly recommend an upgrade to
6.0.29:
