Spring's error handling has been improved(3.2.4), but due to specification changes, excessive logs are now being output. New exception classes will be added to the suppression code.
Details
-> Better protect against concurrent error handling for async requests
ttps://github.com/spring-projects/spring-framework/issues/32340
Several improvements have been made based on the above fixes. We can refer to it from 32340
A side effect of these is the excessive logging that is the issue in this issue.
The exception implies the response is no longer usable, and you can't send any more data. You can treat it in the same way that you would the underlying ClientAbortException or any IOException from the response.
Additional notes
ClientAbort is unavoidable on media servers, so this process is essential. #2640 will reduce the amount of excessive logs. For the rest, the requirement is to simplify the log and even replace it with INFO Level or below.
Prerequisites: #2640
Overview
Spring's error handling has been improved(3.2.4), but due to specification changes, excessive logs are now being output. New exception classes will be added to the suppression code.
Details
-> Better protect against concurrent error handling for async requests
ttps://github.com/spring-projects/spring-framework/issues/32340Several improvements have been made based on the above fixes. We can refer to it from 32340
A side effect of these is the excessive logging that is the issue in this issue.
ttps://github.com/spring-projects/spring-framework/issues/32509Additional notes
ClientAbort is unavoidable on media servers, so this process is essential. #2640 will reduce the amount of excessive logs. For the rest, the requirement is to simplify the log and even replace it with INFO Level or below.