Date of First Response: 2010-02-24 05:54:34 project_key: SOA See linked ESB issue
Link: Added: This issue is related to SOA-1668
Link: Added: This issue depends JBESB-3186
Link: Added: This issue depends JBESB-3187
Link: Added: This issue depends JBESB-3188
Link: Added: This issue depends JBESB-3184
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.
Approved for SOA 4.3 CP03.
Updated in ESB codebase, will be in next merge.
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.
Verified in ER1