You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several places in the ServerRuntime where Jersey is logging exceptions that happen during writing a response. In our scenario, we are using Jetty 12 with EE 10 container over HTTP/2. The client sends a request and aborts it after a specified wait time or because it's no longer interested in the result, which causes the reset frame to be sent to the Jetty server, which closes the response and recycles the request/response objects. When the response is being written/committed while the client aborts the request, ServerRuntime correctly observes IOException thrown by Jetty - these are unrecoverable exception which cannot be mapped to a Response since it's already gone and this would fail as well. I'd like to add a server configuration that will suppress logging of such errors.
I know that I can configure the logger to disable these warnings, but since this is a part of the deployment configuration for some of our customers, we cannot roll this change on our own easily.
There are several places in the ServerRuntime where Jersey is logging exceptions that happen during writing a response. In our scenario, we are using Jetty 12 with EE 10 container over HTTP/2. The client sends a request and aborts it after a specified wait time or because it's no longer interested in the result, which causes the reset frame to be sent to the Jetty server, which closes the response and recycles the request/response objects. When the response is being written/committed while the client aborts the request, ServerRuntime correctly observes IOException thrown by Jetty - these are unrecoverable exception which cannot be mapped to a Response since it's already gone and this would fail as well. I'd like to add a server configuration that will suppress logging of such errors.
I know that I can configure the logger to disable these warnings, but since this is a part of the deployment configuration for some of our customers, we cannot roll this change on our own easily.
I can prepare a PR that will implement this.
cc @jansupol
The text was updated successfully, but these errors were encountered: