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=43002>. 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=43002 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Additional Comments From [EMAIL PROTECTED] 2007-11-09 15:21 ------- Some new information on this issue, so I reopened it. The problem seems to relate to parsing the body content when the **Transfer- Encoding: chunked** header is present. It appears that the chunk length gets corrupted under load and the client is unable to parse the chunk out of the response body. When the NIO connector parameter **socket.appWriteBufSize** is set to a value larger than the total response body, the error condition does not occur. One might succesfully argue that this is proper performance tuning. The Tomcat documents point out that to scale a large number of long held connections, the buffer sizes may need to be less than the response body (the memory footprint would be quite large otherwise). Could there be a race condition involving the response buffering code? I have confirmed this behavior on both JDKs 1.5 and 1.6 on both Windows 2003 and Linux. -- 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]
