Skip to content

RestClient hangs when Destination closes Connection during Request Body Upload #34707

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

Open
mspiess opened this issue Apr 2, 2025 · 1 comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) status: waiting-for-triage An issue we've not yet triaged or decided on

Comments

@mspiess
Copy link

mspiess commented Apr 2, 2025

The client continues to block despite the receiving server having closed the connection already.
Reproduced on Spring Boot version 3.4.4
Works with 3.3.10, likely because that doesn't use io.projectreactor.netty:reactor-netty-http.
Sample application reproducing the bug: https://github.com/mspiess/http-client-bug-reproduction
Find the necessary steps in that repository's README.md.
Excuse the convoluted setup, but I have been unable to reproduce it outside of docker.

The deprecated exchangeTimeout on ReactorClientHttpRequestFactory can be used to force a timeout, but the connection is still leaked.
The other timeout options seem to have no effect.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Apr 2, 2025
@bclozel bclozel transferred this issue from spring-projects/spring-boot Apr 2, 2025
@mspiess
Copy link
Author

mspiess commented Apr 3, 2025

Possibly related to #34178

@jhoeller jhoeller added the in: web Issues in web modules (web, webmvc, webflux, websocket) label Apr 3, 2025
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) status: waiting-for-triage An issue we've not yet triaged or decided on
Projects
None yet
Development

No branches or pull requests

3 participants