Glenn Nielsen wrote:
Not really. The test here reported a lot of connection failures: http://webperformanceinc.com/library/ServletReport/Is there a reported bug you are trying to address?
Tomcat 4.1.17 should improve the results over 4.1.12 (it's faster and would probably lower slightly GC), but I think the number of errors was higher than it should have been.
This could be caused by GC, or possibly because the accepting thread couldn't get the job done, or some other unknown factor.
I have not noticed any problems related to thread scheduling with the medium
volume site I administer.
It is possible that this change could cause threads other than the socket
accept thread to be starved. I would be -1 for making this change unless
there is a significant reported bug that these changes would address.
If it ain't broke, don't fix it. ;-)
Remy
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
