Bug 779647 (SOA-2016)

Summary:	Max total connection number and max connection number per host HTTP client parameters should be set by one parameter
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Jiri Pechanec <jpechane>
Component:	JBossESB	Assignee:	Kevin Conner <kevin.conner>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0.0 GA
Target Milestone:	---
Target Release:	5.1.0.ER2
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2016
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-02 04:19:55 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jiri Pechanec 2010-03-26 15:40:29 UTC

project_key: SOA

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.

Comment 1 Jiri Pechanec 2010-03-26 15:50:51 UTC

Link: Added: This issue is related to JBESB-2841

Comment 2 Anne-Louise Tangring 2010-09-21 20:37:25 UTC

Kevin to check if this is already done for SOA 5.1.0

Comment 3 Kevin Conner 2010-09-22 11:08:56 UTC

Link: Added: This issue depends JBESB-3356

Comment 4 Kevin Conner 2010-09-22 11:09:15 UTC

Should already be present in ER1

Comment 5 Jiri Pechanec 2011-01-11 11:10:36 UTC

Verified in ER6

Comment 6 David Le Sage 2011-03-02 04:14:35 UTC

Temporarily reopening to update release note info.

Comment 7 David Le Sage 2011-03-02 04:19:45 UTC

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.