thanks again for the information. I will go with setting the buffer
then.
peter
Remy Maucherat wrote:
>
> peter lin wrote:
>
> > thanks remy for the information that helps. What if I decide to buffer
> > the response myself in a response wrapper? Does catalina try to call
> > clearBuffer, reset, resetBuffer, flush or flushBuffer in the event a
> > request is passed to my errorpage? Also, does the status code change
> > and the exception set in the request object with
> > request.setAttribute("Throwable") if html has already been sent to the
> > browser?
>
> If you buffer everything, then Jasper will do a forward instead of an
> include.
>
> >
> > In cases where the exception occurs before any content is sent to the
> > browser, it all works fine. I need to ensure exceptions display my
> > custom errorpage, but I'd rather not set the page buffer to an
> > arbitrarily large 64K or 100K.
> >
>
> I think you should, since in the end it should be the same (something
> will need a buffer to hold your bytes, right ?).
> If I were you, I'd try to set a big servlet buffer size rather than a
> big JSP page buffer size (that doesn't run into the issues a servlet
> like Jasper has when trying to recycle things while being thread safe,
> so it would be more efficient; plus it will compute the content-length now).
>
> R�my
>
> --
> 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>
