-
Notifications
You must be signed in to change notification settings - Fork 355
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
NettyConnector does not respect timeouts #5600
Comments
You have tried this with 3.0.13, right? |
I just tried with 3.1.6 and 3.0.13, and timeouts are not respected. |
I've implemented a test to reproduce the described behavior.
and instead of the server being shut down, it only runs indefinitely:
test expects exception to be thrown:
the |
For the timeout issue I was setting connect timeout and read timeout to 60s. I pointed the client at a remote (not localhost) server that was not running. It never connected and never timed out. |
if you modify the given test to use connect tiomeout:
and the target would be
the test still fails with the message:
default connection timeout for the Netty Client is 30s, so if it is not event set, the connection should fail after 30 seconds (I've tested it as well and it behaves so). |
for the 60s custom timeout Netty Client fails as well:
|
I will attempt to reproduce when I get a chance. |
I am using Dropwizard 4 (Jersey 3.0.5) on Java 17.
If I make a request, shutdown the server, and make a subsequent request, it hangs despite setting connection timeout to 30s.
The text was updated successfully, but these errors were encountered: