[
https://issues.apache.org/jira/browse/CAMEL-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13780877#comment-13780877
]
James Carman commented on CAMEL-6670:
-------------------------------------
I have an idea how to fix this, but I don't know about the implementation as it
currently stands. The access to the timePeriodMillis isn't synchronized, but
it's allowed to be modified via JMX, so it probably should be. Perhaps
changing it to AtomicLong?
> Throttler EIP - Add JMX attribute to know if hit limit currently (eg its
> throttling state)
> ------------------------------------------------------------------------------------------
>
> Key: CAMEL-6670
> URL: https://issues.apache.org/jira/browse/CAMEL-6670
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, eip
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: Future
>
>
> See SO
> http://stackoverflow.com/questions/18446689/how-to-get-the-information-that-throttling-limit-has-been-reached
> We would need to extend the org.apache.camel.processor.Throttler so it keeps
> state whether its holding back exchanges due hit limit, or not. Wonder what a
> name should be. It could be a simple boolean to indicate that. And/or a
> counter that counts the number of exchanges being hold back. Then ppl can
> have a graph with the counter.
> This data should be exposed in JMX with
> org.apache.camel.api.management.mbean.ManagedThrottlerMBean
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
