[SMXCOMP-315] ServiceMix http binding component should allow option to create jetty Client per HttpProvider.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.1
• Fix Version/s: 3.2.2, servicemix-http-2008.01
• Component/s: servicemix-http
• Patch Info: Patch Available
• Assignee: Ulhas Bhole
• Reporter: Ulhas Bhole
• Created: 23/Jul/08 11:44
• Updated: 14/Feb/09 22:51
• Resolved: 28/Jul/08 02:46

Description

Currently servicemix-http binding component requires all HttpProviderEndpoints to use one shared jetty HttpClient for request dispatch.
I am attaching a patch which will keep this default behaviour but will allow HttpComponent to configure in such a way that each HttpProviderComponent can have it's own jetty HttpClient.

Currently, bug in jetty HttpClient freezes Servicemix under heavy load when Jetty Threadpool size is lower than maxConnectionPerHost. This fix along with configurable threadpool fix applied by Guillaume will allow servicemix to be more responsive.

I have attached a patch with the Jira.