[
https://issues.apache.org/activemq/browse/SM-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44479#action_44479
]
Ulhas Bhole commented on SM-1478:
---------------------------------
Hi Guillaume,
Good to know about the nio selector stuff. I actually raised JIRA on jetty and
Greg suggested the same but did caution that there are some connection closing
issues which are fixed in Jetty 7.0 and will back port them to Jetty 6 also
(possibly in next release jetty 6.1.12).
Do you think it's good Idea to move to latest Jetty version once 7.0 is release
or stay on Jetty 6?
Also, I think applying this patch also would be good because it's not changing
the default behaviour but gives ability to have some flexibility if someone
requires it.
Regards,
Ulhas Bhole
> 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.
