Skip to content

Stop logging result in WebAsyncManager #33406

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.

Sign up for GitHub

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

Jump to bottom
Closed
sbrannen opened this issue Aug 19, 2024 · 0 comments
Closed

Stop logging result in WebAsyncManager #33406

sbrannen opened this issue Aug 19, 2024 · 0 comments
Assignees
@sbrannen
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone
6.1.13

Comments

@sbrannen
Copy link
Member

Overview

The changes made to WebAsyncManager in conjunction with #32340 resulted in the async result being logged at DEBUG level; whereas, the result was not logged prior to Spring Framework 6.1.5.

Since logging of the result is better left to applications -- for example, via a Filter that is conditionally applied for debugging purposes -- we should stop logging the async result in WebAsyncManager.

Related Issues
@sbrannen sbrannen added in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement labels Aug 19, 2024
@sbrannen sbrannen added this to the 6.1.13 milestone Aug 19, 2024
@sbrannen sbrannen self-assigned this Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sbrannen sbrannen

Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Projects
None yet
Milestone
6.1.13
Development

No branches or pull requests
1 participant
@sbrannen