You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2015/12/01 16:16:45 UTC
[Bug 58657] Spring DeferredResult errorResult response not returned
in async servlet 3.1 mode
https://bz.apache.org/bugzilla/show_bug.cgi?id=58657
--- Comment #10 from Mark Thomas <ma...@apache.org> ---
A little more information for anyone researching this in the future.
Once Tomcat encounters an error, it normally closes the connection. How quickly
it does this depends on the severity of the error. If the error appears to be
mild enough to allow a response to be written, Tomcat will:
- swallow any remaining input
- write the error response
- close the connection
There is a limit to how much input Tomcat will swallow (connector attribute
maxSwallowSize). If more data than this needs to be read, Tomcat will close the
connection immediately without writing an error response. This is because many
clients don't read the response until the request has been fully written.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org