[Bug 66875] Handling async error after spring already handled error

https://bz.apache.org/bugzilla/show_bug.cgi?id=66875 Nils Kohrs changed: What|Removed |Added Component|Catalina|Connectors -- You are receiving this mai

[Bug 66875] Handling async error after spring already handled error

https://bz.apache.org/bugzilla/show_bug.cgi?id=66875 Phillip Webb changed: What|Removed |Added CC||pw...@pivotal.io -- You are receiving

[Bug 66875] Handling async error after spring already handled error

https://bz.apache.org/bugzilla/show_bug.cgi?id=66875 Mark Thomas changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW

[Bug 66875] Handling async error after spring already handled error

https://bz.apache.org/bugzilla/show_bug.cgi?id=66875 Nils Kohrs changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE

[Bug 66875] Handling async error after spring already handled error

https://bz.apache.org/bugzilla/show_bug.cgi?id=66875 Mark Thomas changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug 66875] Handling async error after spring already handled error

https://bz.apache.org/bugzilla/show_bug.cgi?id=66875 --- Comment #4 from Nils Kohrs --- Here is a minimal project to reproduce it: https://github.com/nilskohrs/tomcat-bug-66875 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 66875] Handling async error after spring already handled error

https://bz.apache.org/bugzilla/show_bug.cgi?id=66875 Nils Kohrs changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED

[Bug 66875] Handling async error after spring already handled error

https://bz.apache.org/bugzilla/show_bug.cgi?id=66875 --- Comment #6 from Han Li --- It is indeed possible to reproduce it, here is the debug log: 2023-10-07T18:55:08.622+08:00 DEBUG 10702 --- [o-8080-Acceptor] o.apache.tomcat.util.threads.LimitLatch : Counting up[http-nio-8080-Acceptor] latch=1

[Bug 66875] Handling async error after spring already handled error

https://bz.apache.org/bugzilla/show_bug.cgi?id=66875 --- Comment #7 from Mark Thomas --- The original bug report was for two JSON responses in a single HTTP response. Is that still an issue? Is the error message regarding the response already being committed in addition to the multiple JSON bodi

[Bug 66875] Handling async error after spring already handled error

https://bz.apache.org/bugzilla/show_bug.cgi?id=66875 --- Comment #8 from Han Li --- (In reply to Mark Thomas from comment #7) > The original bug report was for two JSON responses in a single HTTP > response. Is that still an issue? > > Is the error message regarding the response already being co

[Bug 66875] Handling async error after spring already handled error

https://bz.apache.org/bugzilla/show_bug.cgi?id=66875 --- Comment #9 from Mark Thomas --- The simpler test case behaves as desired if the response buffer is flushed after the application provided error response is written. I'm not convinced that the test case completely reproduces the reported is

[Bug 66875] Handling async error after spring already handled error

https://bz.apache.org/bugzilla/show_bug.cgi?id=66875 --- Comment #10 from Mark Thomas --- (In reply to Nils Kohrs from comment #4) > Here is a minimal project to reproduce it: > https://github.com/nilskohrs/tomcat-bug-66875 Thanks. This reproduces the issue as originally described with Tomcat 10

[Bug 66875] Handling async error after spring already handled error

https://bz.apache.org/bugzilla/show_bug.cgi?id=66875 --- Comment #11 from Mark Thomas --- 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

[Bug 66875] Handling async error after spring already handled error

https://bz.apache.org/bugzilla/show_bug.cgi?id=66875 Mark Thomas changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---