Skip to content
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

setMaximumConnectionsPerHost is not limiting the amount of connections per host #401

Closed
jlorgal opened this issue Oct 10, 2013 · 1 comment

Comments

@jlorgal
Copy link

jlorgal commented Oct 10, 2013

I've tested with version 1.7.4 and 1.7.20 (latest) with same results.
The library is not limiting the max amount of concurrent connections to a host however it is working the limit of max connections in total.

builder.setMaximumConnectionsTotal(10);
builder.setMaximumConnectionsPerHost(4);
...

With this configuration, the library open 10 connections to the same host (if there are 10 concurrent requests).

@slandelle
Copy link
Contributor

Hi,

This bug was already referenced, see #201.
This will hopefully get fixed in AHC 2 (not date yet) as it requires some major connection pool refactoring on the Netty provider.

Note that I'm pretty sure it works properly on the Grizzly side, so you could try switching provider.

Closing as duplicate.

cs-workco pushed a commit to cs-workco/async-http-client that referenced this issue Apr 13, 2023
Co-authored-by: George Barnett <gbarnett@apple.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants