https://bz.apache.org/bugzilla/show_bug.cgi?id=66841
--- Comment #2 from Mark Thomas <ma...@apache.org> --- Thanks of the report and the research. That all makes sense. While previous refactoring of error handling has improved things, there are still aspects that I don't like and one of them is CoyoteResponse.setError() returning a boolean value. It looks like that is going to have to be addressed as part of the fix for this issue. My plan is to proceed as follows: - create a test case for this bug based on the description - fix this bug by refactoring AsyncStateMachine.asyncError to be a NO-OP for the second and subsequent calls within an async cycle (cycle == generation in the code) If time allows, I may complete so other refactoring I have in mind for 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
