tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 53174] JIO default maxConnections is not a good default
Date Tue, 01 May 2012 14:09:05 GMT

Mark Thomas <> changed:

           What    |Removed                     |Added
                 OS|                            |All

--- Comment #1 from Mark Thomas <> ---
Read the following for background:

re point 1 - r1099855 should ensure that the behaviour is the same for both
Tomcat 6 and Tomcat 7.

re point 2 - That is true for write but not true for read. With maxConnections
> maxThreads and blocking IO there is always the risk that a connection with
data to read is unable to acquire a thread while all threads are tied up by
connections without data to read.

Reverting the fix has significant impact since it opens up the risk of problems
as described in the thread from a year ago.

With the increasing move towards async, there is an increasinglg strong
argument for making NIO rather than BIO the default and potentially going as
far as dropping the BIO connector all together but that is a debate that
belongs on the dev list not on this issue.

You are receiving this mail because:
You are the assignee for the bug.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message