-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed #12603 Errors logged after cross context dispatch #12606
Conversation
Fixed #12603 Errors logged after cross context dispatch: + Update bytes written in HttpOutput when bypassed by optimization + abort if error dispatch throws
jetty-ee9/jetty-ee9-nested/src/main/java/org/eclipse/jetty/ee9/nested/ServletCoreResponse.java
Show resolved
Hide resolved
@sbordet @janbartel review please! |
ExceptionUtil.addSuppressedIfNotAssociated(x, t); | ||
throw x; | ||
} | ||
abort(x); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The logic is now completely different from before... Is that ok?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's what I'm asking you as the reviewer!)
The issue was that we have an exception whilst trying to write an error page and we handle it by trying to write an error page.... which resulted in a nasty loop. I think aborting if an error page cannot be generated is the best thing to do
jetty-ee9/jetty-ee9-nested/src/main/java/org/eclipse/jetty/ee9/nested/ServletCoreResponse.java
Outdated
Show resolved
Hide resolved
Fix ee10 also
This issue is somewhat related to #11325 |
Waiting on CI green before I merge and stage 12.0.16 |
Fixed #12603 Errors logged after cross context dispatch: