[
https://issues.apache.org/jira/browse/KNOX-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979369#comment-14979369
]
Kevin Minder commented on KNOX-604:
-----------------------------------
Added a property in gateway-site.xml as shown below. This sets both the max
total connections for each httpclient instance and the max connection per route
to the same value. The default value is 32.
{code}
<property>
<name>gateway.httpclient.maxConnections</name>
<value>32</value>
</property>
{code}
Can also set this on a per service basis with a service param
httpclient.maxConnections.
> 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)
