Ok, I'm back to answer my own question :)
I figured out that this will let me increase the number of simultaneous
connections per route and total:
// >> ConnectionManager
// Setting max connections per route.
ConnPerRoute connPerRoute = new ConnPerRouteBean(12);
ConnManagerParams.setMaxConnectionsPerRoute(params, connPerRoute);
ConnManagerParams.setMaxTotalConnections(params, 20);
connMan = new ThreadSafeClientConnManager(params, schemeRegistry);
Also, it seems like the Twitter API simply doesn't allow keep alive.
jpswain wrote:
>
> Hi,
> Oleg, I think your answer explains why I can't seem to get more than 2
> simultaneous connections during my development here. I can't seem to find
> out how to se the max connections per route. Could you tell me how to do
> this?
>
> Also, I'm running logging in debug mode so I can see all the "wire" and
> header statements, and even though all my requests to the Twitter REST API
> say "Keep-Alive" and I get "Keep-Alive" responses in the headers I can't
> seem to find a way to reuse any connections.
>
>
--
View this message in context:
http://www.nabble.com/MAX-CONNECTIONS-tp21858014p22964871.html
Sent from the HttpClient-User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
