https://issues.apache.org/bugzilla/show_bug.cgi?id=53174
Priority: P2
Bug ID: 53174
Assignee: dev@tomcat.apache.org
Summary: JIO default maxConnections is not a good default
Severity: normal
Classification: Unclassified
Reporter: fha...@apache.org
Hardware: PC
Status: NEW
Version: 7.0.27
Component: Connectors
Product: Tomcat 7
http://svn.apache.org/viewvc?view=revision&revision=1099855
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.
