DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8992>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8992 IE6/XP: Limitation of POST Area within HTTP request? ------- Additional Comments From [EMAIL PROTECTED] 2002-06-10 14:48 ------- The "socketCloseDelay='250'" appears to solve the problem. The element to modify within server.xml is Http10Connector not Http10Interceptor. The modified element should appear as follows: <Http10Connector port="8080" secure="false" maxThreads="100" maxSpareThreads="50" minSpareThreads="10" socketCloseDelay="250" /> In tracking down where socketCloseDelay is used within Tomcat (used in Http10Interceptor) it is used as a value for a Thread.sleep before TcpConnection.shutDownInput is called. It appears that by using this call to Thread.sleep, a race condition is occuring on the XP platform for the default value. It would seem that the preferred method would be to set "tcpNoDelay" to true. However, I set the member variable "tcpNoDelay" of the PoolTcpEndpoint class to be true. I then rebuilt the class, and updated the container/tomcat_util.jar file. This should cause the incoming socket to not use Nagle's algorithm when sending TCP/IP packets, but for some reason this did not rectify the problem. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
