[
https://issues.apache.org/jira/browse/CAMEL-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977191#action_12977191
]
Claus Ibsen commented on CAMEL-1902:
------------------------------------
java.util.Timer is actually discouraged to be used. You should use a
ScheduledExecutorService instead.
There is a ExectuorServiceStrategy you access from CamelContext which has APIs
for providing such a scheduler to you. This ensures that Camel can handle its
lifecycle, and 3rd party can plugin a custom provider for thread pools, such as
from a JEE server. Thus its best to leverage this.
> ThroughputLogger - Add ability to be timer based
> ------------------------------------------------
>
> Key: CAMEL-1902
> URL: https://issues.apache.org/jira/browse/CAMEL-1902
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 2.0-M3
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.7.0
>
> Attachments: camel-core-throughputLogger-groupFrequency.txt
>
>
> The ThroughputLogger is based on a size so it reports when X messages has
> passed it.
> What is needed is to be able to say it should report every X period instead.
> And add option to not report before first message have arrived.
> And add option to not report if the value was 0 for the 2nd time in case of a
> long inactivity period
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
