https://issues.apache.org/bugzilla/show_bug.cgi?id=54928
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Mark Thomas <ma...@apache.org> ---
(In reply to comment #2)
> Okay, I see. It looks like one has to dispatch before calling
> asyncContext.complete().
In this case you need the dispatch to get the request back onto a container
thread where the error handling can deal with the error. It is this bit I am
not 100% is what is intended by the spec but I can't find any clear
definitions.
> I opened this ticket because of the exception but I
> didn't realize it was illegal ot call complete() from a non-container
> thread. Maybe that can be detected and rejected with a message to that
> extent.
It is perfectly valid to call complete() from a non-container thread.
Again, the users list is the place to discuss this.
--
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
