Red Hat Bugzilla – Bug 779647
Max total connection number and max connection number per host HTTP client parameters should be set by one parameter
Last modified: 2011-03-01 23:19:55 EST
SOAPProxy, HttpRouter etc are using Apache HTTP client to implement HTTP invocation. But the URL for both of these actions are static so they will always point to the same host. So the both parameters should be set to the same value and it thus does not make sense to configure them separately.
Link: Added: This issue is related to JBESB-2841
Kevin to check if this is already done for SOA 5.1.0
Link: Added: This issue depends JBESB-3356
Should already be present in ER1
Verified in ER6
Temporarily reopening to update release note info.
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/JBESB-3356
The SOAPProxy, SOAPClient and HttpRouter all use the Apache HTTP client to implement HTTP invocation. As the URLs for these actions are static, they always point to the same host. Previously, the values for the maximum total connections and maximum connections per host HTTP for each of these clients had to be set individually. Users can now set via a single parameter instead.