On a related note to flushing. I've discovered a bug, but don't want to file one until I know for sure it's not a duplicate of the other flush bugs already in bugzilla.
The bug is the following: if a page throws an exception and an errorPage directive is set, the resulting error page will print out anything left over from the parent page and the errorpage. That means <html> .... and everything preceding the exception is written to the browser. One way around this I found was to set the buffer to a large size, like buffer="64K". To reproduce the bug: create a page with some html (has to be more than the default buffer size), towards the bottom throw an exception. create a custom error page. using a browser load the page and the resulting out put should contain html from both pages. This bug can be reproduced with autFlush set to true and false. If people are busy, I'm willing to spend a couple hours going through the code to find a fix and submit a patch. If it's not a bug, any pointers would be appreciated. peter lin Remy Maucherat wrote: > > I was wondering if people have been testing Jasper 2 from Tomcat 5 with > flushing disabled. If testing is ok (Watchdog is, but from my experience > it's not enough ;-) ), I would be willing to port it to the 4.1.x > branch. I have yet to see a problem using the latest Tomcat 5 code (I > think it's a good sign). > > Comments ? > > After that, I plan to tag 4.1.15. > > Remy > > -- > To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
