[
https://issues.apache.org/jira/browse/CAMEL-25530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-25530.
---------------------------------
Resolution: Fixed
> camel-timer - the includeMetadata option names the exchange properties it
> sets, and that CamelTimerCounter starts at 1
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-25530
> URL: https://issues.apache.org/jira/browse/CAMEL-25530
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.23.0
>
>
> The description of the includeMetadata option says "such as fired time, timer
> name, timer count etc.". The names of the exchange properties, and that the
> counter is 1 on the first fire, are only in the header table of the component
> page, not in the catalog that tools read.
> In the local-model benchmark (pick a file by the timer counter) models
> assumed CamelTimerCounter starts at 0 in 6 of 12 runs; most found out after a
> failed run, one did not and failed.
> Improvement: the description names CamelTimerCounter (the fire count, 1 on
> the first fire), CamelTimerName, CamelTimerPeriod, CamelTimerFiredTime,
> CamelTimerTime (when the time option is set) and the headers
> CamelTimerFiredTime and CamelMessageTimestamp.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
