-
Notifications
You must be signed in to change notification settings - Fork 38.3k
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
Blockhound flags a blocking call when WebFlux serves a static resource #26631
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: enhancement
A general enhancement
Milestone
Comments
Thanks @JanVdloock. As discussed on Gitter this should be a Framework issue. We’ll transfer it over. |
spring-projects-issues
added
the
status: waiting-for-triage
An issue we've not yet triaged or decided on
label
Mar 2, 2021
From Gitter:
|
rstoyanchev
added
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: enhancement
A general enhancement
and removed
status: waiting-for-triage
An issue we've not yet triaged or decided on
labels
Mar 5, 2021
We can create a Blockhound rule to suppress it since this only happens once. |
rstoyanchev
changed the title
Spring Boot Webflux has a blocking call while reading properties when unexisting static content is requested
Blockhound flags a blocking call when WebFlux serves a static resource
Mar 5, 2021
lxbzmy
pushed a commit
to lxbzmy/spring-framework
that referenced
this issue
Mar 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: enhancement
A general enhancement
Using Spring Boot WebFlux 2.4.3, there are blocking calls, detected by BlockHound when properties are loaded during the call.
Program was run with JDK 11 on Windows 10.
A simple program is attached. It contains a few static images, but when a unexisting image is requested, BlockHound detects a blocking call when the framework reads a properties file, to find the configuration for the error handling.
See the test class in the attached program.
spring-reactor-webflux-blockhound properties.zip
The text was updated successfully, but these errors were encountered: