[
https://issues.apache.org/activemq/browse/SMXCOMP-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50241#action_50241
]
Ron Gavlin commented on SMXCOMP-457:
------------------------------------
Chris,
Would it make sense to extend this throttling framework in certain cases beyond
simply polling endpoints? Specifically, I am thinking of the smx-jms consumer
(see https://issues.apache.org/activemq/browse/SMXCOMP-98). In this case,
rather than skipping/controlling a poll, it would explicitly manage the Spring
JMS concurrentConsumers.
I suspect at least some aspects of the configuration and runtime management of
the throttling mechanism could be shared beyond simply polling endpoints.
Thoughts?
/Ron
> Add throttling framework for polling endpoints
> ----------------------------------------------
>
> Key: SMXCOMP-457
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-457
> Project: ServiceMix Components
> Issue Type: New Feature
> Components: servicemix-file, servicemix-ftp, servicemix-mail,
> servicemix-vfs
> Affects Versions: servicemix-file-2008.01, servicemix-ftp-2008.01,
> servicemix-mail-2008.01
> Reporter: Chris Custine
> Assignee: Chris Custine
>
> While working on SMXCOMP-52 it became apparent that each polling endpoint has
> a need for some sort of throttling now that many of them are using the async
> send() method. It would be nice to add a feature that allows configurable
> throttling policies on each endpoint and its possible that we could allow
> configuration and management of throttling config at runtime possibly through
> JMX.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
