-
Notifications
You must be signed in to change notification settings - Fork 63
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
Consider a max wait in pool manager #654
Labels
Comments
What type of timer? One for connections, thread pool, or something else? |
Connections. If it takes you N seconds to borrow a connection, the request fails and the borrow is canceled. |
Is this not addressed by final class ClientChannelFactory(
bufferSize: Int = DefaultBufferSize,
group: Option[AsynchronousChannelGroup] = None,
channelOptions: ChannelOptions = ChannelOptions.DefaultOptions,
scheduler: TickWheelExecutor = Execution.scheduler,
connectTimeout: Duration = Duration.Inf) |
I don't think so. I think |
Thanks for clarifying. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
http4s/http4s#796 was a bug, but it's too easy to deadlock a server. We should consider a timer so borrows don't hang indefinitely for the next time we or our an app does something stupid.
The text was updated successfully, but these errors were encountered: