Thanks for the thoughts... few things inline....
> > 2. Does your unexpectedError.jsp use sessions? Does it have <%...@page > session="false"%>? No, I don't think so. I'll have to check into this. > 3. If the response was already partially sent to the client and you > receive an "unexpected" error (while rendering some further part of > the page), it is not easy to properly handle this error outside of the > page that causes it.... > > If that issue is caused by some executable code on your JSP page (I > have not seen your auditLog.jsp , so I do not know),... It is, kind of. The auditLog.jsp is streaming back results from a very slow operation. I think (though my logging when it occurred wasn't good enough to be sure) that the exception that started the chain of events was the user navigating away from the page, before it finished sending the data. The next time my jsp page tried to flush the buffer, it took an error. > >> I don't care >> about the error, other than I don't want it to appear in the log file >> as a "SEVERE: Exception " because that generates support tickets.... >> > > 4. If such unexpected errors on some page are happening regularly I > personally would consider that a serious fault, which deserves a > support ticket. Though being unable to locate the source of the error > due to a faulty error handling page does not help much. As long as I am right this is all a side-effect of the user navigating away before the page completes... then I just need to make it go away :) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
