https://bz.apache.org/bugzilla/show_bug.cgi?id=58323
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Mark Thomas <ma...@apache.org> ---
Logging unhandled errors at ERROR level has been the convention in Tomcat for
as long as I can remember and isn't going to change.
Any exceptions in the service() method are up to the application to handle.
Only it can determine how serious they are and only the application can
determine what cleaning up - if any - is required after the error.
While most applications won't be concerned about an I/O error, I have worked
with apps where any I/O trigger the destruction of the session, the logging out
of the user and a security alert. Tomcat has no way to determine which sort of
app has been deployed.
As an aside, as soon as the I/O occurs - and before the exception even reaches
the servlet - Tomcat will have marked the connection as faultly and be waiting
to close it.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
