https://bz.apache.org/bugzilla/show_bug.cgi?id=61768
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
The first time an attempt is made to perform I/O after the client disconnects
then the following will happen:
- The code attempting to perform the I/O will see an I/O exception
If one or more AsyncListeners are configured:
- Tomcat will call the onError event for any registered AsyncListeners.
It is expected that one of those listeners will complete the AsycnContext.
If no listeners are configured:
- Tomcat will complete the AsyncContext
Tomcat will then go on to recycle the various objects used for the request
since processing of that request is now complete.
If the application/framework needs to perform clean-up if an error occurs then
it is the responsibility of the application/framework to register the
appropriate listener(s) and perform that clean-up in response to an error.
If there is a scenario where an I/O error occurs and Tomcat does not trigger
the async error handling then that would be a Tomcat bug. However, that is not
the case here. That the processor has been recycled means that Tomcat has
triggered the async error handling.
--
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
