https://bz.apache.org/bugzilla/show_bug.cgi?id=58323
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
That stack trace originates inside Servlet.service(). Tomcat has no way to tell
if the problem is a trivial one that is safe to ignore or a serious one that
needs to be logged. Therefore, such errors are always logged at ERROR.
Even if Tomcat is able to detect that it is due to a client abort exception,
Tomcat still doens't know how serious an issue that is for any given
application.
Applications are expected to catch and handle such errors appropriately.
--
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
