When using the new Reactive REST Client, any readTimeout or connectTimeout you set is being ignored. Usually, you can either set it directly at the RestClientBuilder or alternatively via com.acme.MyClient/mp-rest/connectTimeout / com.acme.MyClient/mp-rest/readTimeout. No matter if you use the RestClientBuilder or the property, the value is not honored, requests run infinitely if the server does not answer.
Expected behavior
If a connectTimeout or readTimeout is set, the request / subscription should be cancelled, even if it is non-blocking.
Actual behavior
Requests never time out.
To Reproduce
Link to a small reproducer (preferably a Maven project if the issue is not Gradle-specific).
Or attach an archive containing the reproducer to the issue.
Steps to reproduce the behavior:
Create small project with Reactive REST client which queries an endpoint that delays the answer for a long time, e.g. 15 seconds.
You will receive the answer of the request after 15 seconds.
Even after configuring the connectTimeout or readTimeout as specified above, you still receive the answer after 15 seconds.
Configuration
# Add your application.properties here, if applicable.
Screenshots
(If applicable, add screenshots to help explain your problem.)
Environment (please complete the following information):
Output of uname -a or ver
Microsoft Windows [Version 10.0.18363.1556]
Output of java -version
OpenJDK 64-Bit Server VM Corretto-11.0.10.9.1 (build 11.0.10+9-LTS, mixed mode)
GraalVM version (if different from Java)
N/A
Quarkus version or git rev
2.0.0.CR2
Build tool (ie. output of mvnw --version or gradlew --version)
Describe the bug
When using the new Reactive REST Client, any readTimeout or connectTimeout you set is being ignored. Usually, you can either set it directly at the RestClientBuilder or alternatively via
com.acme.MyClient/mp-rest/connectTimeout/com.acme.MyClient/mp-rest/readTimeout. No matter if you use the RestClientBuilder or the property, the value is not honored, requests run infinitely if the server does not answer.Expected behavior
If a connectTimeout or readTimeout is set, the request / subscription should be cancelled, even if it is non-blocking.
Actual behavior
Requests never time out.
To Reproduce
Link to a small reproducer (preferably a Maven project if the issue is not Gradle-specific).
Or attach an archive containing the reproducer to the issue.
Steps to reproduce the behavior:
Configuration
Screenshots
(If applicable, add screenshots to help explain your problem.)
Environment (please complete the following information):
Output of
uname -aorverMicrosoft Windows [Version 10.0.18363.1556]
Output of
java -versionOpenJDK 64-Bit Server VM Corretto-11.0.10.9.1 (build 11.0.10+9-LTS, mixed mode)
GraalVM version (if different from Java)
N/A
Quarkus version or git rev
2.0.0.CR2
Build tool (ie. output of
mvnw --versionorgradlew --version)Apache Maven 3.6.3
Additional context
(Add any other context about the problem here.)
https://github.com/quarkusio/quarkus/issues/17526
$upstream:17526$