[
https://issues.apache.org/activemq/browse/SM-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44545#action_44545
]
Gert Vanthienen commented on SM-1478:
-------------------------------------
Fixed for 3.2 branch in
http://svn.eu.apache.org/viewvc?view=rev&revision=679817. Thank you for
providing the patch!
Unfortunately, this patch cannot be applied to the components trunk. Could you
make a new one for that?
> ServiceMix http binding component should allow option to create jetty Client
> per HttpProvider.
> ----------------------------------------------------------------------------------------------
>
> Key: SM-1478
> URL: https://issues.apache.org/activemq/browse/SM-1478
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-http
> Affects Versions: 3.2.1
> Reporter: Ulhas Bhole
> Assignee: Ulhas Bhole
> Attachments: jettyClientPerProvider.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
