tomcat-dev mailing list archives

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

          Priority: P2
            Bug ID: 53174
           Summary: JIO default maxConnections is not a good default
          Severity: normal
    Classification: Unclassified
          Hardware: PC
            Status: NEW
           Version: 7.0.27
         Component: Connectors
           Product: Tomcat 7

This feature automatically sets maxConnections to maxThreads. It has a negative
effect for the following reasons

1. It completely changes behavior from Tomcat 6 to 7, and unless one reads the
fine print, one will never find out

2. In servlet 3.0, with the introduction of async servlets, there is a way to
keep a connection open without having a worker thread associated with it.

For case 2. the system SHOULD be able to handle this type of usage through its
default configuration. 

Reverting this fix, and correcting the documentation has no foreseeable impact
on systems that get upgraded with the next release of Tomcat

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

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