[
https://jira.jboss.org/jira/browse/JBESB-2548?page=com.atlassian.jira.plu...
]
Tom Fennelly closed JBESB-2548.
-------------------------------
Resolution: Done
trunk: 27118
Added the "max-connections-per-host" configuration to the Connection
Configurator. Didn't add any SOAPClient or HttpRouter specific settings. They can
use "max-connections-per-host" also and we can add specific settings later if
requested.
HttpClientFactory not configuring the
"default-max-connections-per-host" on the connection manager
--------------------------------------------------------------------------------------------------
Key: JBESB-2548
URL:
https://jira.jboss.org/jira/browse/JBESB-2548
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.5
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Fix For: 4.6
Attachments: default-connections-per-host.patch
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