https://bz.apache.org/bugzilla/show_bug.cgi?id=66875
--- Comment #11 from Mark Thomas <ma...@apache.org> --- I think there are two separate issues here. 1. When Spring sets jakarta.servlet.error.exception that triggers Tomcat's internal error handling. Whether Spring should do that and whether that should have the effect it has are the first issue. 2. Tomcat's error handling triggers the onError event. As per SRV.2.3.3.3 (search for "error dispatch") if no listeners call complete() or dispatch() this triggers another error dispatch. It is this second error dispatch that is generating the second error message. Spring and/or the application should be calling complete() or dispatch() as a result of the onError() event. This is the second issue. Next steps are to do some more research on the first issue. -- 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
