-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Honor read timeout in reactive rest client #19223
Conversation
This workflow status is outdated as a new workflow run has been triggered. 🚫 This workflow run has been cancelled. Failing Jobs - Building 8119002
|
...time/src/main/java/org/jboss/resteasy/reactive/client/handlers/ClientSendRequestHandler.java
Outdated
Show resolved
Hide resolved
@@ -197,8 +195,8 @@ public Response get() { | |||
throw new BlockingNotAllowedException(); | |||
} | |||
try { | |||
return c.get(readTimeoutMs, TimeUnit.MILLISECONDS); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is no longer needed (and is actually incorrect) as the timeout handling is performed by Vert.x
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it would be great to have a test for it :)
Before this change the read timeout only had an effect when doing a synchronous call (and even then it didn't result in the proper Vert.x exception) The connect timeout handling doesn't need any changes because it is properly handled when org.jboss.resteasy.reactive.client.impl.ClientImpl is created Fixes: quarkusio#17526
Yeah, that's a good follow up :) |
This workflow status is outdated as a new workflow run has been triggered. 🚫 This workflow run has been cancelled. Failing Jobs - Building f6cd978
|
Follow up on: quarkusio#19223
Follow up on: quarkusio#19223
Add test for rest-client reactive timeout
Before this change the read timeout only had an effect when doing
a synchronous call (and even then it didn't result in the proper Vert.x exception)
The connect timeout handling doesn't need any changes because it is properly handled
when org.jboss.resteasy.reactive.client.impl.ClientImpl is created
Fixes: #17526