DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=21983>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=21983 ------- Additional Comments From [EMAIL PROTECTED] 2005-03-31 12:12 ------- William said that the benefit is tiny. But I don't think so. It often happens that MaxClient of Apache is large and may not be changed. Assuming that MaxClient is 1000, 1) maxThreads=1000 connectionTimeout=0 acceptCount=10 2) maxThreads=100 connectionTimeout=2000 acceptCount=1000 1) is recommended in docs/website. But 2) achieved a better throughput under heavy load. Too many working threads are not preferable, you know. When I choose 2) setting, queueing is really needed. To enable acceptCount, I did this test with a fixed ChannelSocket. ------------------ line 114: int backlog=50; line 258: public void setBacklog(int i) { backlog = i; } line 323: sSocket=new ServerSocket( i, backlog, inet ); ----------------- Bug#21983 is marked as WONTFIX because this is related to JK2. But this fix can be done in Tomcat-side. I hope this will be reopened and fixed. (Or Should I move this bug report to JK category?) # It is said that a ServerSocket is created with a zero backlog. # But If a zero value is given for the backlog-argument, default backlog size (= 50) will be applied. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
