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=14760>. 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=14760 Array overflow exception in InternalOutputBuffer ------- Additional Comments From [EMAIL PROTECTED] 2002-11-22 13:56 ------- After further investigation I can now reproduce this at will with a small test webapp (see attachment). It appears to happen when a request is interrupted (for example by the user clicking on another app url after selecting an initial url which is taking some time to come back). The final request is served correctly but the InternalOutputBuffer associated with the interrupted request fills up with many calls to the write() method. If the originally requested page is big enough (as demonstrated in the web app attached to this report) the output buffer will overflow. To see this: Deploy the war file. Load the index.jsp file. Click on two of the links in quick succession. Check the log file - at some point you will see the out of bounds exception. I have also modified the InternalOutputBuffer code (source on request) to provide logging on the 'pos' variable and I can see that it is increasing with many calls to write(String) or write(MessageBytes) before the overflow occurs. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
