[esb-issues] [JBoss JIRA] Updated: (JBESB-2804) Merge JBESB-2548: HttpClientFactory not configuring the "default-max-connections-per-host" on the connection manager
Tom Fennelly (JIRA)
jira-events at lists.jboss.org
Fri Aug 28 07:09:23 EDT 2009
[ https://jira.jboss.org/jira/browse/JBESB-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Fennelly updated JBESB-2804:
--------------------------------
Fix Version/s: 4.4 CP3
(was: 4.6)
Affects Version/s: 4.4 CP2
(was: 4.5)
> Merge JBESB-2548: HttpClientFactory not configuring the "default-max-connections-per-host" on the connection manager
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBESB-2804
> URL: https://jira.jboss.org/jira/browse/JBESB-2804
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Transports
> Affects Versions: 4.4 CP2
> Reporter: Tom Fennelly
> Assignee: Tom Fennelly
> Fix For: 4.4 CP3
>
>
> HttpClientFactory.createHttpClient creates a HttpConnectionManager instance and configures the "max-total-connections". This is somewhat irrelevant however as the HttpClient still has a default limit of 1 (or 2 - I forget) max connections per connected host, so will never use anything like the configured "max-total-connections".
> One fix is to also set the "default-max-connections-per-host" on the HostConnectionManager params, with a default value of the value returned from a call to HttpConnectionManager.getParams().getMaxTotalConnections(). I think this would be fine because we only ever have 1 host per httpclient, but you could also provide an override config for situations where we have more.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the esb-issues
mailing list