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=40719>. 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=40719 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2007-08-04 12:29 ------- Im the original submitter for this bug. This bug is NOT just related to header sizes. It seems to ALSO trigger when there is a large amount of page compilation/parsing errors which cause a servlet exception to be thrown and then the container forwards to a error page. Also happens during other random times. Tomcat dies during this internal forward process with this exact same stack trace. NO HEADERS have been sent to the client at this stage NOR have ANY HEADERS BEEN SET. To sum up: NO HEADERS (via addHeader or whatever) are being set to trigger this bug. Is tomcat erronesously using the same internal buffers to store internal parse/compilation errors as the output header buffer ? -- 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]
