Bug 779593 (SOA-1963)

Summary:	HttpClient on different services shares configuration
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Jiri Pechanec <jpechane>
Component:	JBossESB	Assignee:	Kevin Conner <kevin.conner>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.3 CP02	CC:	dlesage
Target Milestone:	---
Target Release:	4.3 CP04 ER1
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1963
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-03-26 15:05:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Deadline:	2010-03-08

Description Jiri Pechanec 2010-02-24 10:21:39 UTC

Date of First Response: 2010-02-24 05:54:34
project_key: SOA

See linked ESB issue

Comment 1 Kevin Conner 2010-02-24 10:23:54 UTC

Link: Added: This issue is related to SOA-1668

Comment 2 Kevin Conner 2010-02-24 10:25:05 UTC

Link: Added: This issue depends JBESB-3186

Comment 3 Kevin Conner 2010-02-24 10:48:58 UTC

Link: Added: This issue depends JBESB-3187

Comment 4 Kevin Conner 2010-02-24 10:51:32 UTC

Link: Added: This issue depends JBESB-3188

Comment 5 Kevin Conner 2010-02-24 10:53:19 UTC

Link: Added: This issue depends JBESB-3184

Comment 6 Kevin Conner 2010-02-24 10:54:34 UTC

I have decided to link the four known issues to this as they are inter-linked.  This issue can be resolved once all four have been addressed.

Comment 7 Anne-Louise Tangring 2010-02-25 15:39:24 UTC

Approved for SOA 4.3 CP03.

Comment 8 Kevin Conner 2010-03-04 22:24:07 UTC

Updated in ESB codebase, will be in next merge.

Comment 9 David Le Sage 2010-03-10 04:17:31 UTC

Draft text for the Resolved Issues section of the Release Notes states:


https://jira.jboss.org/jira/browse/SOA-1963

    A number of problems were being caused by the fact that the HttpClient on different services
    was sharing a single configuration. Consequentially, HttpClient connection parameters were
    being ignored, SOAPClient and EsbWsdlLoader on different services were incorrectly sharing
    configurations and, finally, HttpProtocol would reference a static protocol upon redeployment
    of a service, (forcing other services to use its address).

    The default mapping in HttpClient was being overwritten on each invocation. By rectifying this,
    the problems have now been resolved and each protocol is now using the expected default.

Comment 10 Jiri Pechanec 2010-03-26 15:05:58 UTC

Verified in ER1