https://bz.apache.org/bugzilla/show_bug.cgi?id=68227
Bug ID: 68227
Summary: AsyncListener::onComplete is not called on network
error if error listener calls dispatch
Product: Tomcat 10
Version: 10.1.16
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: Servlet
Assignee: dev@tomcat.apache.org
Reporter: jedenh...@righthub.com
Target Milestone: ------
In the event of a network error, AsyncListener::onComplete is not called if the
preceding call to AsyncListener::onError results in a call to
AsyncContext::dispatch.
This behaviour is observed starting with Tomcat 10.1.12 as well as 10.1.16
(latest as of this writing). This behaviour is not observed in 10.1.11.
I have created two reproducers here: https://gitlab.com/-/snippets/3625015
One reproducer uses Spring Boot, and closely mirrors our production code. The
other reproducer uses plain tomcat-embed, and was used by myself to figure out
if this was a bug in Tomcat or in Spring.
The call to AsyncContext::dispatch is key to triggering this behaviour, without
that the call to AsyncListener::onComplete occurs as expected.
--
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
