You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/10/28 23:20:27 UTC
[jira] [Commented] (KNOX-604) Expose configuration of HttpClient's
max connections per route setting
[ https://issues.apache.org/jira/browse/KNOX-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979366#comment-14979366 ]
ASF subversion and git services commented on KNOX-604:
------------------------------------------------------
Commit 8a057724991d1ba0c38d3619b9aada265faf8674 in knox's branch refs/heads/master from [~kevin.minder]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=8a05772 ]
KNOX-604: Expose configuration of HttpClient's max connections per route setting
> Expose configuration of HttpClient's max connections per route setting
> ----------------------------------------------------------------------
>
> Key: KNOX-604
> URL: https://issues.apache.org/jira/browse/KNOX-604
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Kevin Minder
> Assignee: Kevin Minder
> Fix For: 0.7.0
>
>
> The httpClient should allow configurable “max connection per route”, “ max total connections”. Currently the GatewayDispatchFilter.init() configures the HttpClient with default connection pool, which is too small.
> httpClient = HttpClients.custom().setDefaultCookieStore(new NoCookieStore()).build();
> change to:
> httpClient = HttpClients.custom().setDefaultCookieStore(new NoCookieStore()).setMaxConnPerRoute(…) .setMaxConnTotal(…).build();
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)